Update text for RESET CONNECTION:

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

diff --git a/doc/TODO b/doc/TODO
index 57b417b73eb2d002f3287565499cb0197a9ac0bc..62002c00b1e4aea8bd395e6fc42f15fc0dcac14f 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Jun  6 18:03:40 EDT 2005
+Last updated:      Mon Jun  6 21:59:31 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -454,9 +454,13 @@ Commands
 * 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

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index eb6f7fa255641b8b625d8c0d40a88898e88b7fb2..f5d004d6d3056e3bd4ad8d9a92e8accac69b91ff 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 Jun  6 18:03:40 EDT 2005
+Last updated:           Mon Jun  6 21:59:31 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -417,9 +417,13 @@ first.
   Make row-wise comparisons work per SQL spec
   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