database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Move LISTEN/NOTIFY items to separate TODO section.

Browse Source
This commit is contained in:
Bruce Momjian
2008-04-15 15:07:09 +00:00
parent c28c9d69ef
commit 6d2b258ad0
2 changed files with 39 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
doc/TODO
View File

@ -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
=====================