summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2006-04-09 03:27:06 +0000
committerBruce Momjian2006-04-09 03:27:06 +0000
commit83843a4439f7c3106a36728cecc83565da3a2765 (patch)
treec566e81881c6f616630ce612e2287e82c605fb6f
parent898eb25431847e2c79ba6a9c93e36b2bd75a25bc (diff)
Update:
> * Allow the creation of indexes with mixed ascending/descending > specifiers > > This is possible now by creating an operator class with reversed sort > operators. One complexity is that NULLs would then appear at the start > of the result set, and this might affect certain sort types, like > merge join. >
-rw-r--r--doc/TODO11
-rw-r--r--doc/src/FAQ/TODO.html10
2 files changed, 17 insertions, 4 deletions
diff --git a/doc/TODO b/doc/TODO
index 206705a0d10..d788d34ceee 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Mon Mar 6 17:51:00 EST 2006
+Last updated: Sat Apr 8 23:26:57 EDT 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -827,7 +827,14 @@ Indexes
* Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
* Add fillfactor to control reserved free space during index creation
-* Allow the creation of indexes with mixed ascending/descending specifiers
+* Allow the creation of indexes with mixed ascending/descending
+ specifiers
+
+ This is possible now by creating an operator class with reversed sort
+ operators. One complexity is that NULLs would then appear at the start
+ of the result set, and this might affect certain sort types, like
+ merge join.
+
* Allow constraint_exclusion to work for UNIONs like it does for
inheritance, allow it to work for UPDATE and DELETE statements, and allow
it to be used for all statements with little performance impact
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 5cc6eb94631..9091a9accf5 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated: Mon Mar 6 17:51:00 EST 2006
+Last updated: Sat Apr 8 23:26:57 EDT 2006
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -752,7 +752,13 @@ first.
</li><li>Allow accurate statistics to be collected on indexes with more than
one column or expression indexes, perhaps using per-index statistics
</li><li>Add fillfactor to control reserved free space during index creation
- </li><li>Allow the creation of indexes with mixed ascending/descending specifiers
+ </li><li>Allow the creation of indexes with mixed ascending/descending
+ specifiers
+<p> This is possible now by creating an operator class with reversed sort
+ operators. One complexity is that NULLs would then appear at the start
+ of the result set, and this might affect certain sort types, like
+ merge join.
+</p>
</li><li>Allow constraint_exclusion to work for UNIONs like it does for
inheritance, allow it to work for UPDATE and DELETE statements, and allow
it to be used for all statements with little performance impact