diff options
| author | Bruce Momjian | 2008-04-15 15:07:09 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2008-04-15 15:07:09 +0000 |
| commit | 6d2b258ad022744ee2980b0d8781931ebf66308c (patch) | |
| tree | 74fb30487f6c8d988aba4ecef74f2feaccb7b414 /doc/TODO | |
| parent | c28c9d69ef1afe73295cfe8712efeba1bf7845d9 (diff) | |
Move LISTEN/NOTIFY items to separate TODO section.
Diffstat (limited to 'doc/TODO')
| -rw-r--r-- | doc/TODO | 38 |
1 files changed, 21 insertions, 17 deletions
@@ -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 ===================== |