From bdfa8e5e71e4deb80f8f04779178b921919b69ed Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 26 Aug 2005 19:10:48 +0000
Subject: Update constraint_exclusion items:
< inheritance, and allow it to work for UPDATE and DELETE queries
> inheritance, allow it to work for UPDATE and DELETE queries, and allow
> it to be used for all queries with little performance impact
< * Allow constraint_elimination to be automatically performed
<
< This requires additional code to reduce the performance loss caused by
< constraint elimination.
---
doc/src/FAQ/TODO.html | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index f9679375016..4b84782b737 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Fri Aug 26 14:59:39 EDT 2005
+Last updated: Fri Aug 26 15:10:29 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -622,7 +622,8 @@ first.
Add fillfactor to control reserved free space during index creation
Allow the creation of indexes with mixed ascending/descending specifiers
Allow constraint_exclusion to work for UNIONs like it does for
- inheritance, and allow it to work for UPDATE and DELETE queries
+ inheritance, allow it to work for UPDATE and DELETE queries, and allow
+ it to be used for all queries with little performance impact
GIST
- Add more GIST index support for geometric data types
@@ -822,10 +823,6 @@ first.
Log queries where the optimizer row estimates were dramatically
different from the number of rows actually found?
- Allow constraint_elimination to be automatically performed
- This requires additional code to reduce the performance loss caused by
- constraint elimination.
-
--
cgit v1.2.3