PostgreSQL TODO List
====================
-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
http://www.postgresql.org/docs/faqs.TODO.html.
* Add NOVICE output level for helpful messages like automatic sequence/index
creation
-* Add RESET CONNECTION 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 RESET SESSION command to reset all session state
* Add GUC to issue notice about statements that use unjoined tables
* Allow EXPLAIN to identify tables that were skipped because of
constraint_exclusion
-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
Add NOVICE output level for helpful messages like automatic sequence/index
creation
-
Add RESET CONNECTION 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.
-
+
-Add RESET SESSION command to reset all session state
Add GUC to issue notice about statements that use unjoined tables
Allow EXPLAIN to identify tables that were skipped because of
constraint_exclusion