Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit6d2b258

Browse files
committed
Move LISTEN/NOTIFY items to separate TODO section.
1 parentc28c9d6 commit6d2b258

File tree

2 files changed

+39
-31
lines changed

2 files changed

+39
-31
lines changed

‎doc/TODO‎

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
PostgreSQL TODO List
22
====================
33
Current maintainer:Bruce Momjian (bruce@momjian.us)
4-
Last updated:Tue Apr 1510:24:22 EDT 2008
4+
Last updated:Tue Apr 1511:06:48 EDT 2008
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -601,22 +601,6 @@ SQL Commands
601601

602602
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
603603

604-
* Allow LISTEN/NOTIFY to store info in memory rather than tables?
605-
606-
Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
607-
such information in memory would improve performance.
608-
609-
* Add optional textual message to NOTIFY
610-
611-
This would allow an informational message to be added to the notify
612-
message, perhaps indicating the row modified or other custom
613-
information.
614-
615-
* Allow multiple identical NOTIFY events to always be communicated to the
616-
client, rather than sent as a single notification to the listener
617-
618-
http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
619-
620604
* Add a GUC variable to warn about non-standard SQL usage in queries
621605
* Add SQL-standard MERGE command, typically used to merge two tables
622606
[merge]
@@ -878,6 +862,26 @@ SQL Commands
878862
ANALYZE, and CLUSTER
879863

880864

865+
* LISTEN/NOTIFY
866+
867+
o Allow LISTEN/NOTIFY to store info in memory rather than tables?
868+
869+
Currently LISTEN/NOTIFY information is stored in pg_listener.
870+
Storing such information in memory would improve performance.
871+
872+
o Add optional textual message to NOTIFY
873+
874+
This would allow an informational message to be added to the notify
875+
message, perhaps indicating the row modified or other custom
876+
information.
877+
878+
o Allow multiple identical NOTIFY events to always be communicated
879+
to the client, rather than sent as a single notification to the
880+
listener
881+
882+
http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php
883+
884+
881885

882886
Referential Integrity
883887
=====================

‎doc/src/FAQ/TODO.html‎

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Tue Apr 1510:24:22 EDT 2008
11+
Last updated: Tue Apr 1511:06:48 EDT 2008
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -522,19 +522,6 @@ <h1><a name="section_7">SQL Commands</a></h1>
522522
</p>
523523
</li><li>Improve logging of prepared transactions recovered during startup
524524
<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php</a>
525-
</p>
526-
</li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
527-
<p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
528-
such information in memory would improve performance.
529-
</p>
530-
</li><li>Add optional textual message to NOTIFY
531-
<p> This would allow an informational message to be added to the notify
532-
message, perhaps indicating the row modified or other custom
533-
information.
534-
</p>
535-
</li><li>Allow multiple identical NOTIFY events to always be communicated to the
536-
client, rather than sent as a single notification to the listener
537-
<p><ahref="http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php">http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php</a>
538525
</p>
539526
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries
540527
</li><li>Add SQL-standard MERGE command, typically used to merge two tables
@@ -758,6 +745,23 @@ <h1><a name="section_7">SQL Commands</a></h1>
758745
<li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
759746
ANALYZE, and CLUSTER
760747
</li></ul>
748+
</li><li>LISTEN/NOTIFY
749+
<ul>
750+
<li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
751+
<p> Currently LISTEN/NOTIFY information is stored in pg_listener.
752+
Storing such information in memory would improve performance.
753+
</p>
754+
</li><li>Add optional textual message to NOTIFY
755+
<p> This would allow an informational message to be added to the notify
756+
message, perhaps indicating the row modified or other custom
757+
information.
758+
</p>
759+
</li><li>Allow multiple identical NOTIFY events to always be communicated
760+
to the client, rather than sent as a single notification to the
761+
listener
762+
<p><ahref="http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php">http://archives.postgresql.org/pgsql-general/2008-01/msg00057.php</a>
763+
</p>
764+
</li></ul>
761765
</li></ul>
762766
<h1><aname="section_8">Referential Integrity</a></h1>
763767

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp