Add URL to RESET CONNECTION:

<   notify the protocol when a RESET CONNECTION command is used.
>   notify the protocol when a RESET CONNECTION command is used.  See
>   http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
>   for a partial implementation.

diff --git a/doc/TODO b/doc/TODO
index adfa1c496c92072688944211720f99c8c157b0d5..a0f3ff8f6ae9f897d9d49eb04f9349d023404734 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Jun  6 09:52:15 EDT 2006
+Last updated:      Tue Jun  6 12:27:12 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -455,7 +455,9 @@ 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 CONNECTION command is used.  See
+  http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
+  for a partial implementation.
 
 * 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 75d9a652aa8de6f2cab9b3b311f2227db6c422dc..a63c1b529887068e772171a63c54cd750c1f4c22 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:           Tue Jun  6 09:52:15 EDT 2006
+Last updated:           Tue Jun  6 12:27:12 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -418,7 +418,9 @@ 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 CONNECTION command is used.  See
+  http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
+  for a partial implementation.
 
   Add GUC to issue notice about statements that use unjoined tables
   Allow EXPLAIN to identify tables that were skipped because of