From: Bruce Momjian Date: Tue, 7 Jun 2005 01:59:39 +0000 (+0000) Subject: Update text for RESET CONNECTION: X-Git-Tag: REL8_1_0BETA1~626 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0f011f6daae65963cc29a1208bf662a7c13056c3;p=postgresql Update text for RESET CONNECTION: < all temporary tables, removal of any NOTIFYs, cursors, prepared < queries(?), currval()s, etc. This could be used for connection pooling. < We could also change RESET ALL to have this functionality. > 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. --- diff --git a/doc/TODO b/doc/TODO index 57b417b73e..62002c00b1 100644 --- a/doc/TODO +++ b/doc/TODO @@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Mon Jun 6 18:03:40 EDT 2005 +Last updated: Mon Jun 6 21:59:31 EDT 2005 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -454,9 +454,13 @@ Commands * Add RESET CONNECTION command to reset all session state This would include resetting of all variables (RESET ALL), dropping of - all temporary tables, removal of any NOTIFYs, cursors, prepared - queries(?), currval()s, etc. This could be used for connection pooling. - We could also change RESET ALL to have this functionality. + 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. * Allow FOR UPDATE queries to do NOWAIT locks * Add GUC to issue notice about queries that use unjoined tables diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index eb6f7fa255..f5d004d6d3 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Mon Jun 6 18:03:40 EDT 2005 +Last updated: Mon Jun 6 21:59:31 EDT 2005

The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. @@ -417,9 +417,13 @@ first.

Make row-wise comparisons work per SQL spec

Add RESET CONNECTION command to reset all session state

This would include resetting of all variables (RESET ALL), dropping of - all temporary tables, removal of any NOTIFYs, cursors, prepared - queries(?), currval()s, etc. This could be used for connection pooling. - We could also change RESET ALL to have this functionality. + 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.

Allow FOR UPDATE queries to do NOWAIT locks

Add GUC to issue notice about queries that use unjoined tables