RESET SESSION is more precise:

< * Add RESET CONNECTION command to reset all session state
> * Add RESET SESSION command to reset all session state
447c447
<   notify the protocol when a RESET CONNECTION command is used.
>   notify the protocol when a RESET SESSION command is used.

diff --git a/doc/TODO b/doc/TODO
index 14bd5f546c6da480aec569ac1d19a2eff10ccceb..9503022d7090d6bb503594ec289585b3f46064be 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Apr 24 22:58:22 EDT 2006
+Last updated:      Tue Apr 25 10:30:50 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -435,7 +435,7 @@ SQL Commands
   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
+* 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,
@@ -444,7 +444,7 @@ SQL Commands
   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.
+  notify the protocol when a RESET SESSION command is used.
 
 * Add GUC to issue notice about statements that use unjoined tables
 * Allow EXPLAIN to identify tables that were skipped because of 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index f7ac2693497a275c39855d978e4fda9fbebd5188..0bd124634d576ba14d302166b3b2a25700a99ba6 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Mon Apr 24 22:58:22 EDT 2006
+Last updated:           Tue Apr 25 10:30:50 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -400,7 +400,7 @@ first.
   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
+  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
@@ -408,7 +408,7 @@ first.
   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.
+  notify the protocol when a RESET SESSION command is used.
 
   Add GUC to issue notice about statements that use unjoined tables
   Allow EXPLAIN to identify tables that were skipped because of