mirror of
https://github.com/postgres/postgres.git
synced 2025-04-25 21:42:33 +03:00
Done:
> * -Add RESET SESSION command to reset all session state
This commit is contained in:
parent
995ba280c1
commit
c0e42e9325
15
doc/TODO
15
doc/TODO
@ -2,7 +2,7 @@
|
|||||||
PostgreSQL TODO List
|
PostgreSQL TODO List
|
||||||
====================
|
====================
|
||||||
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
Current maintainer: Bruce Momjian (bruce@momjian.us)
|
||||||
Last updated: Wed Apr 11 17:02:21 EDT 2007
|
Last updated: Thu Apr 12 15:38:17 EDT 2007
|
||||||
|
|
||||||
The most recent version of this document can be viewed at
|
The most recent version of this document can be viewed at
|
||||||
http://www.postgresql.org/docs/faqs.TODO.html.
|
http://www.postgresql.org/docs/faqs.TODO.html.
|
||||||
@ -521,18 +521,7 @@ SQL Commands
|
|||||||
|
|
||||||
* Add NOVICE output level for helpful messages like automatic sequence/index
|
* Add NOVICE output level for helpful messages like automatic sequence/index
|
||||||
creation
|
creation
|
||||||
* Add RESET CONNECTION command to reset all session state
|
* -Add RESET SESSION 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,
|
|
||||||
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.
|
|
||||||
http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
|
|
||||||
|
|
||||||
* Add GUC to issue notice about statements that use unjoined tables
|
* Add GUC to issue notice about statements that use unjoined tables
|
||||||
* Allow EXPLAIN to identify tables that were skipped because of
|
* Allow EXPLAIN to identify tables that were skipped because of
|
||||||
constraint_exclusion
|
constraint_exclusion
|
||||||
|
@ -8,7 +8,7 @@
|
|||||||
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
|
||||||
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
|
<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/>
|
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
|
||||||
Last updated: Wed Apr 11 17:02:21 EDT 2007
|
Last updated: Thu Apr 12 15:38:17 EDT 2007
|
||||||
</p>
|
</p>
|
||||||
<p>The most recent version of this document can be viewed at<br/>
|
<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>.
|
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
|
||||||
@ -464,17 +464,7 @@ first. There is also a developer's wiki at<br/>
|
|||||||
</p>
|
</p>
|
||||||
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
|
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
|
||||||
creation
|
creation
|
||||||
</li><li>Add RESET CONNECTION command to reset all session state
|
</li><li>-<em>Add RESET SESSION command to reset all session state</em>
|
||||||
<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 RESET CONNECTION command is used.
|
|
||||||
<a href="http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php">http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php</a>
|
|
||||||
</p>
|
|
||||||
</li><li>Add GUC to issue notice about statements that use unjoined tables
|
</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
|
</li><li>Allow EXPLAIN to identify tables that were skipped because of
|
||||||
constraint_exclusion
|
constraint_exclusion
|
||||||
|
Loading…
x
Reference in New Issue
Block a user