PostgreSQL TODO List

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

Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)

Last updated:Thu Dec22 18:05:31 EST 2005

Last updated:Mon Dec26 00:14:46 EST 2005

The most recent version of this document can be viewed at

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

* %Add COMMENT ON for all cluster global objects (roles, databases

and tablespaces)

* %Make row-wise comparisons work per SQL spec

Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but

the SQL standard requires it to be processed as a column-by-column

comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.

* Add RESET CONNECTION command to reset all session state

This would include resetting of all variables (RESET ALL), dropping of

<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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>

Last updated:Thu Dec22 18:05:31 EST 2005

Last updated:Mon Dec26 00:14:46 EST 2005

<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>%Add COMMENT ON for all cluster global objects (roles, databases

and tablespaces)

</li><li>%Make row-wise comparisons work per SQL spec

<p> Right now, '(a, b) &lt; (1, 2)' is processed as 'a &lt; 1 and b &lt; 2', but

the SQL standard requires it to be processed as a column-by-column

comparison, so the proper comparison is '(a &lt; 1) OR (a = 1 AND b &lt; 2)'.

</li><li>Add RESET CONNECTION command to reset all session state

<p> This would include resetting of all variables (RESET ALL), dropping of

temporary tables, removing any NOTIFYs, cursors, open transactions,