Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitc0e42e9

Browse files
committed
Done:
> * -Add RESET SESSION command to reset all session state
1 parent995ba28 commitc0e42e9

File tree

2 files changed

+4
-25
lines changed

2 files changed

+4
-25
lines changed

‎doc/TODO

Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (bruce@momjian.us)
5-
Last updated:Wed Apr11 17:02:21 EDT 2007
5+
Last updated:Thu Apr12 15:38:17 EDT 2007
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -521,18 +521,7 @@ SQL Commands
521521

522522
* Add NOVICE output level for helpful messages like automatic sequence/index
523523
creation
524-
* Add RESET CONNECTION command to reset all session state
525-
526-
This would include resetting of all variables (RESET ALL), dropping of
527-
temporary tables, removing any NOTIFYs, cursors, open transactions,
528-
prepared queries, currval()s, etc. This could be used for connection
529-
pooling. We could also change RESET ALL to have this functionality.
530-
The difficult of this features is allowing RESET ALL to not affect
531-
changes made by the interface driver for its internal use. One idea
532-
is for this to be a protocol-only feature. Another approach is to
533-
notify the protocol when a RESET CONNECTION command is used.
534-
http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
535-
524+
* -Add RESET SESSION command to reset all session state
536525
* Add GUC to issue notice about statements that use unjoined tables
537526
* Allow EXPLAIN to identify tables that were skipped because of
538527
constraint_exclusion

‎doc/src/FAQ/TODO.html

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Wed Apr11 17:02:21 EDT 2007
11+
Last updated:Thu Apr12 15:38:17 EDT 2007
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -464,17 +464,7 @@ <h1><a name="section_8">SQL Commands</a></h1>
464464
</p>
465465
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
466466
creation
467-
</li><li>Add RESET CONNECTION command to reset all session state
468-
<p> This would include resetting of all variables (RESET ALL), dropping of
469-
temporary tables, removing any NOTIFYs, cursors, open transactions,
470-
prepared queries, currval()s, etc. This could be used for connection
471-
pooling. We could also change RESET ALL to have this functionality.
472-
The difficult of this features is allowing RESET ALL to not affect
473-
changes made by the interface driver for its internal use. One idea
474-
is for this to be a protocol-only feature. Another approach is to
475-
notify the protocol when a RESET CONNECTION command is used.
476-
<ahref="http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php">http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php</a>
477-
</p>
467+
</li><li>-<em>Add RESET SESSION command to reset all session state</em>
478468
</li><li>Add GUC to issue notice about statements that use unjoined tables
479469
</li><li>Allow EXPLAIN to identify tables that were skipped because of
480470
constraint_exclusion

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp