Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
c0e42e93
Commit
c0e42e93
authored
Apr 12, 2007
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Done:
> * -Add RESET SESSION command to reset all session state
parent
995ba280
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
25 deletions
+4
-25
doc/TODO
doc/TODO
+2
-13
doc/src/FAQ/TODO.html
doc/src/FAQ/TODO.html
+2
-12
No files found.
doc/TODO
View file @
c0e42e93
...
...
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated:
Wed Apr 11 17:02:21
EDT 2007
Last updated:
Thu Apr 12 15:38:17
EDT 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
...
...
@@ -521,18 +521,7 @@ SQL Commands
* Add NOVICE output level for helpful messages like automatic sequence/index
creation
* 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,
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 CONNECTION command is used.
http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
* -Add RESET SESSION command to reset all session state
* Add GUC to issue notice about statements that use unjoined tables
* Allow EXPLAIN to identify tables that were skipped because of
constraint_exclusion
...
...
doc/src/FAQ/TODO.html
View file @
c0e42e93
...
...
@@ -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:bruce@momjian.us"
>
bruce@momjian.us
</a>
)
<br/>
Last updated:
Wed Apr 11 17:02:21
EDT 2007
Last updated:
Thu Apr 12 15:38:17
EDT 2007
</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>
.
...
...
@@ -464,17 +464,7 @@ first. There is also a developer's wiki at<br/>
</p>
</li><li>
Add NOVICE output level for helpful messages like automatic sequence/index
creation
</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 CONNECTION command is used.
<a
href=
"http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php"
>
http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
</a>
</p>
</li><li>
-
<em>
Add RESET SESSION command to reset all session state
</em>
</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
constraint_exclusion
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment