I now see we support RESET SESSION AUTHORIZATION, so it seems we have to

bmomjian · bmomjian · commit 5fd7df43e290 · 2006-04-25T14:33:41.000Z
use RESET CONNECTION:

&lt; * Add RESET SESSION command to reset all session state
&gt; * Add RESET CONNECTION command to reset all session state
447c447
&lt;   notify the protocol when a RESET SESSION command is used.
&gt;   notify the protocol when a RESET CONNECTION command is used.
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 Apr 25 10:30:50 EDT 2006
+Last updated:		Tue Apr 25 10:33:19 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 SESSION command to reset all session state
+* 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,
@@ -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 SESSION command is used.
+  notify the protocol when a RESET CONNECTION 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
@@ -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 Apr 25 10:30:50 EDT 2006
+Last updated:           Tue Apr 25 10:33:19 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>.
@@ -400,15 +400,15 @@ <h1><a name="section_8">SQL Commands</a></h1>
   the SQL standard requires it to be processed as a column-by-column
   comparison, so the proper comparison is '(a &lt; 1) OR (a = 1 AND b &lt; 2)'.
 </p>
-  </li><li>Add RESET SESSION command to reset all session state
+  </li><li>Add RESET CONNECTION command to reset all session state
 <p>  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 SESSION command is used.
+  notify the protocol when a RESET CONNECTION command is used.
 </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 
