Add URL to RESET CONNECTION:

bmomjian · bmomjian · commit 05631354f358 · 2006-06-06T16:27:23.000Z
< 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
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:	Bruce Momjian (pgman@candle.pha.pa.us)
-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
@@ -8,7 +8,7 @@
 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
 <h1><a name="section_1">PostgreSQL TODO List</a></h1>
 <p>Current maintainer:     Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
-Last updated:           Tue Jun  6 09:52:15 EDT 2006
+Last updated:           Tue Jun  6 12:27:12 EDT 2006
 </p>
 <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>.
@@ -418,7 +418,9 @@ <h1><a name="section_8">SQL Commands</a></h1>
   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
+  <a href="http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php">http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php</a>
+  for a partial implementation.
 </p>
   </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 
