public inbox for [email protected]
help / color / mirror / Atom feedFrom: Fujii Masao <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: indexterm of pg_notify
Date: Tue, 18 May 2010 11:15:20 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Tue, May 18, 2010 at 4:39 AM, Alvaro Herrera <[email protected]> wrote:
> Excerpts from Tom Lane's message of lun may 17 11:38:29 -0400 2010:
>
>> Yeah, the link would be less useful if it just pointed to the whole
>> page. It would be nice though if the index entry said something more
>> specific than "Notes", perhaps "NOTIFY Notes". Is there a way to
>> control the label used for an index link?
>
> Doesn't look like there is :-(
How about creating new subsection "pg_notify" under "Notes" and placing
the description about pg_notify in it? Here is the patch.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachments:
[application/octet-stream] pg_notify_indexterm_v2.patch (1.7K, 2-pg_notify_indexterm_v2.patch)
download | inline diff:
*** a/doc/src/sgml/ref/notify.sgml
--- b/doc/src/sgml/ref/notify.sgml
***************
*** 152,169 **** NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
<refsect1>
<title>Notes</title>
- <indexterm>
- <primary>pg_notify</primary>
- </indexterm>
-
- <para>
- To send a notification you can also use the function
- <literal><function>pg_notify</function>(<type>text</type>,
- <type>text</type>)</literal>. 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 <command>NOTIFY</command> command if you need to work with
- non-constant channel names and payloads.
- </para>
<para>
There is a queue that holds notifications that have been sent but not
yet processed by all listening sessions. If this queue becomes full,
--- 152,157 ----
***************
*** 180,185 **** NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
--- 168,190 ----
A transaction that has executed <command>NOTIFY</command> cannot be
prepared for two-phase commit.
</para>
+
+ <refsect2>
+ <title>pg_notify</title>
+
+ <indexterm>
+ <primary>pg_notify</primary>
+ </indexterm>
+
+ <para>
+ To send a notification you can also use the function
+ <literal><function>pg_notify</function>(<type>text</type>,
+ <type>text</type>)</literal>. 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 <command>NOTIFY</command> command if you need to work with
+ non-constant channel names and payloads.
+ </para>
+ </refsect2>
</refsect1>
<refsect1>
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: indexterm of pg_notify
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox