PostgreSQL TODO List

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

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

Last updated:Mon Jun 618:03:40 EDT 2005

Last updated:Mon Jun 621:59:31 EDT 2005

The most recent version of this document can be viewed at

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

* Add RESET CONNECTION command to reset all session state

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

all temporary tables, removal of any NOTIFYs, cursors, prepared

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

We could also change RESET ALL to have this functionality.

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 RESET CONNECTION command is used.

* Allow FOR UPDATE queries to do NOWAIT locks

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

<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 Jun 618:03:40 EDT 2005

Last updated: Mon Jun 621:59:31 EDT 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>Make row-wise comparisons work per SQL spec

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

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

all temporary tables, removal of any NOTIFYs, cursors, prepared

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

We could also change RESET ALL to have this functionality.

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 RESET CONNECTION command is used.

</li><li>Allow FOR UPDATE queries to do NOWAIT locks

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