From: Robert Haas Date: Tue, 18 May 2010 02:28:53 +0000 (+0000) Subject: Move pg_notify() details to a subsection within the NOTIFY reference page. X-Git-Tag: REL9_0_BETA2~100 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=11f2efd12ac134d82d75255750c6bad685f05686;p=postgresql Move pg_notify() details to a subsection within the NOTIFY reference page. This allows the index to reference the pg_notify() subsection specifically, rather than Notes section of the NOTIFY reference page more generally. Fujii Masao --- diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml index 33b491e1e7..ccdbe3da51 100644 --- a/doc/src/sgml/ref/notify.sgml +++ b/doc/src/sgml/ref/notify.sgml @@ -1,5 +1,5 @@ @@ -152,18 +152,6 @@ NOTIFY channel [ , Notes - - pg_notify - - - - To send a notification you can also use the function - pg_notify(text, - text). The function takes the channel name as the - first argument and the payload as the second. The function is much easier - to use than the NOTIFY command if you need to work with - non-constant channel names and payloads. - There is a queue that holds notifications that have been sent but not yet processed by all listening sessions. If this queue becomes full, @@ -180,6 +168,23 @@ NOTIFY channel [ , NOTIFY cannot be prepared for two-phase commit. + + + pg_notify + + + pg_notify + + + + To send a notification you can also use the function + pg_notify(text, + text). The function takes the channel name as the + first argument and the payload as the second. The function is much easier + to use than the NOTIFY command if you need to work with + non-constant channel names and payloads. + +