mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-18 18:44:06 +08:00
Done:
< * Allow the creation of indexes with mixed ascending/descending > * -Allow the creation of indexes with mixed ascending/descending < < 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. <
This commit is contained in:
parent
833f9cb7b8
commit
b0452cd87d
10
doc/TODO
10
doc/TODO
@ -2,7 +2,7 @@
|
||||
PostgreSQL TODO List
|
||||
====================
|
||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||
Last updated: Sat Jan 6 17:55:06 EST 2007
|
||||
Last updated: Mon Jan 8 22:43:23 EST 2007
|
||||
|
||||
The most recent version of this document can be viewed at
|
||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||
@ -882,14 +882,8 @@ Indexes
|
||||
|
||||
* Allow accurate statistics to be collected on indexes with more than
|
||||
one column or expression indexes, perhaps using per-index statistics
|
||||
* Allow the creation of indexes with mixed ascending/descending
|
||||
* -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
|
||||
|
@ -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:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
||||
Last updated: Sat Jan 6 17:55:06 EST 2007
|
||||
Last updated: Mon Jan 8 22:43:23 EST 2007
|
||||
</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>.
|
||||
@ -796,13 +796,8 @@ first.
|
||||
</p>
|
||||
</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>Allow the creation of indexes with mixed ascending/descending
|
||||
</li><li>-<em>Allow the creation of indexes with mixed ascending/descending</em>
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user