Move LISTEN/NOTIFY items to separate TODO section.

diff --git a/doc/TODO b/doc/TODO
index b9723bf8468992cdd79a6cc4d391338bc4e14fe7..8eff9ab9406f0369dd3c1a4efc16469e1fdda0fb 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Apr 15 10:24:22 EDT 2008
+Last updated:      Tue Apr 15 11:06:48 EDT 2008
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -601,22 +601,6 @@ SQL Commands
 
   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
 
-* Allow LISTEN/NOTIFY to store info in memory rather than tables?
-
-  Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
-  such information in memory would improve performance.
-
-* Add optional textual message to NOTIFY
-
-  This would allow an informational message to be added to the notify
-  message, perhaps indicating the row modified or other custom
-  information.
-
-* Allow multiple identical NOTIFY events to always be communicated to the
-  client, rather than sent as a single notification to the listener
-
-  http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
-
 * Add a GUC variable to warn about non-standard SQL usage in queries
 * Add SQL-standard MERGE command, typically used to merge two tables
   [merge]
@@ -878,6 +862,26 @@ SQL Commands
      ANALYZE, and CLUSTER
 
 
+* LISTEN/NOTIFY
+
+   o Allow LISTEN/NOTIFY to store info in memory rather than tables?
+
+     Currently LISTEN/NOTIFY information is stored in pg_listener. 
+     Storing such information in memory would improve performance.
+
+   o Add optional textual message to NOTIFY
+
+     This would allow an informational message to be added to the notify
+     message, perhaps indicating the row modified or other custom
+     information.
+
+   o Allow multiple identical NOTIFY events to always be communicated
+     to the client, rather than sent as a single notification to the
+     listener
+
+     http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
+
+
 
 Referential Integrity
 =====================

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 00e4e8818ebd09c1c8182afb383ef03112beb8f7..56971190c5cb418bdf4ba874b51fd0862ab5e544 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Tue Apr 15 10:24:22 EDT 2008
+Last updated:           Tue Apr 15 11:06:48 EDT 2008
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -522,19 +522,6 @@ first.  There is also a developer's wiki at
 
   Improve logging of prepared transactions recovered during startup
   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
-
-  Allow LISTEN/NOTIFY to store info in memory rather than tables?
-  Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
-  such information in memory would improve performance.
-
-  Add optional textual message to NOTIFY
-  This would allow an informational message to be added to the notify
-  message, perhaps indicating the row modified or other custom
-  information.
-
-  Allow multiple identical NOTIFY events to always be communicated to the
-  client, rather than sent as a single notification to the listener
-  http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
 
   Add a GUC variable to warn about non-standard SQL usage in queries
   Add SQL-standard MERGE command, typically used to merge two tables
@@ -758,6 +745,23 @@ first.  There is also a developer's wiki at
     Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
           ANALYZE, and CLUSTER
   
+  LISTEN/NOTIFY
+  
+    Allow LISTEN/NOTIFY to store info in memory rather than tables?
+          Currently LISTEN/NOTIFY information is stored in pg_listener. 
+          Storing such information in memory would improve performance.
+
+    Add optional textual message to NOTIFY
+          This would allow an informational message to be added to the notify
+          message, perhaps indicating the row modified or other custom
+          information.
+
+    Allow multiple identical NOTIFY events to always be communicated
+          to the client, rather than sent as a single notification to the
+          listener
+          http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
+
+  
 
 Referential Integrity