PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (bruce@momjian.us)

Last updated:Sat Jan6 17:55:06 EST 2007

Last updated:Mon Jan8 22:43:23 EST 2007

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

* 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

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>

Last updated:Sat Jan6 17:55:06 EST 2007

Last updated:Mon Jan8 22:43:23 EST 2007

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

</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.

</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