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.
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]
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
=====================
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
-Last updated: Tue Apr 15 10:24:22 EDT 2008
+Last updated: Tue Apr 15 11:06:48 EDT 2008
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
</li><li>Improve logging of prepared transactions recovered during startup
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php</a>
</p>
- </li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
-<p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
- such information in memory would improve performance.
-</p>
- </li><li>Add optional textual message to NOTIFY
-<p> This would allow an informational message to be added to the notify
- message, perhaps indicating the row modified or other custom
- information.
-</p>
- </li><li>Allow multiple identical NOTIFY events to always be communicated to the
- client, rather than sent as a single notification to the listener
-<p> <a href="http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php">http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php</a>
-</p>
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries
</li><li>Add SQL-standard MERGE command, typically used to merge two tables
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
<li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
ANALYZE, and CLUSTER
</li></ul>
+ </li><li>LISTEN/NOTIFY
+ <ul>
+ <li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
+<p> Currently LISTEN/NOTIFY information is stored in pg_listener.
+ Storing such information in memory would improve performance.
+</p>
+ </li><li>Add optional textual message to NOTIFY
+<p> This would allow an informational message to be added to the notify
+ message, perhaps indicating the row modified or other custom
+ information.
+</p>
+ </li><li>Allow multiple identical NOTIFY events to always be communicated
+ to the client, rather than sent as a single notification to the
+ listener
+<p> <a href="http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php">http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php</a>
+</p>
+ </li></ul>
</li></ul>
<h1><a name="section_8">Referential Integrity</a></h1>
OSDN Git Service
