PostgreSQL TODO List

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

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

Last updated:Mon Apr24 22:58:22 EDT 2006

Last updated:Tue Apr25 10:30:50 EDT 2006

The most recent version of this document can be viewed at

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

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 RESETCONNECTION command to reset all session state

* Add RESETSESSION command to reset all session state

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

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

The difficult of this features is allowing RESET ALL to not affect

changes made by the interface driver for its internal use. One idea

is for this to be a protocol-only feature. Another approach is to

notify the protocol when a RESETCONNECTION command is used.

notify the protocol when a RESETSESSION command is used.

* Add GUC to issue notice about statements that use unjoined tables

* Allow EXPLAIN to identify tables that were skipped because 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:Mon Apr24 22:58:22 EDT 2006

Last updated:Tue Apr25 10:30:50 EDT 2006

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

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 RESETCONNECTION command to reset all session state

</li><li>Add RESETSESSION 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,

prepared queries, currval()s, etc. This could be used for connection

pooling. We could also change RESET ALL to have this functionality.

The difficult of this features is allowing RESET ALL to not affect

changes made by the interface driver for its internal use. One idea

is for this to be a protocol-only feature. Another approach is to

notify the protocol when a RESETCONNECTION command is used.

notify the protocol when a RESETSESSION command is used.

</li><li>Add GUC to issue notice about statements that use unjoined tables

</li><li>Allow EXPLAIN to identify tables that were skipped because of