From 6d2b258ad022744ee2980b0d8781931ebf66308c Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 15 Apr 2008 15:07:09 +0000 Subject: [PATCH] Move LISTEN/NOTIFY items to separate TODO section. --- doc/TODO | 38 +++++++++++++++++++++----------------- doc/src/FAQ/TODO.html | 32 ++++++++++++++++++-------------- 2 files changed, 39 insertions(+), 31 deletions(-) diff --git a/doc/TODO b/doc/TODO index b9723bf846..8eff9ab940 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -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 00e4e8818e..56971190c5 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-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. @@ -523,19 +523,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 [merge] @@ -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 +

    • Referential Integrity

    -- 2.11.0