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 33b491e1e7c1cb76eef324c294649444444cb7ec..ccdbe3da515b363dcde02ce00366bf5882fd8fa1 100644 (file)
--- 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 [ , 
    A transaction that has executed 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.
+   
+