mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-11-27 07:21:09 +08:00
I now see we support RESET SESSION AUTHORIZATION, so it seems we have to
use RESET CONNECTION: < * Add RESET SESSION command to reset all session state > * Add RESET CONNECTION command to reset all session state 447c447 < notify the protocol when a RESET SESSION command is used. > notify the protocol when a RESET CONNECTION command is used.
This commit is contained in:
parent
2b70093548
commit
5fd7df43e2
6
doc/TODO
6
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
|
||||
|
@ -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,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)'.
|
||||
</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
|
||||
@ -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 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
|
||||
|
Loading…
Reference in New Issue
Block a user