1999-07-22 17:09:15 +02:00
|
|
|
<!--
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
$PostgreSQL: pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.29 2007/01/31 23:26:04 momjian Exp $
|
2001-12-08 04:24:40 +01:00
|
|
|
PostgreSQL documentation
|
1999-07-22 17:09:15 +02:00
|
|
|
-->
|
|
|
|
|
1999-07-14 22:32:59 +02:00
|
|
|
<refentry id="SQL-UNLISTEN">
|
|
|
|
<refmeta>
|
2003-09-15 05:32:24 +02:00
|
|
|
<refentrytitle id="SQL-UNLISTEN-TITLE">UNLISTEN</refentrytitle>
|
1999-07-14 22:32:59 +02:00
|
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
|
|
</refmeta>
|
2003-04-27 01:56:51 +02:00
|
|
|
|
1999-07-14 22:32:59 +02:00
|
|
|
<refnamediv>
|
2003-04-27 01:56:51 +02:00
|
|
|
<refname>UNLISTEN</refname>
|
|
|
|
<refpurpose>stop listening for a notification</refpurpose>
|
1999-07-14 22:32:59 +02:00
|
|
|
</refnamediv>
|
2003-04-27 01:56:51 +02:00
|
|
|
|
2003-08-31 19:32:24 +02:00
|
|
|
<indexterm zone="sql-unlisten">
|
|
|
|
<primary>UNLISTEN</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
1999-07-14 22:32:59 +02:00
|
|
|
<refsynopsisdiv>
|
2003-04-27 01:56:51 +02:00
|
|
|
<synopsis>
|
|
|
|
UNLISTEN { <replaceable class="PARAMETER">name</replaceable> | * }
|
|
|
|
</synopsis>
|
1999-07-14 22:32:59 +02:00
|
|
|
</refsynopsisdiv>
|
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
1999-07-14 22:32:59 +02:00
|
|
|
|
|
|
|
<para>
|
2003-04-27 01:56:51 +02:00
|
|
|
<command>UNLISTEN</command> is used to remove an existing
|
|
|
|
registration for <command>NOTIFY</command> events.
|
|
|
|
<command>UNLISTEN</command> cancels any existing registration of
|
|
|
|
the current <productname>PostgreSQL</productname> session as a
|
|
|
|
listener on the notification <replaceable
|
|
|
|
class="PARAMETER">name</replaceable>. The special wildcard
|
|
|
|
<literal>*</literal> cancels all listener registrations for the
|
|
|
|
current session.
|
1999-07-14 22:32:59 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2000-12-26 00:15:27 +01:00
|
|
|
<xref endterm="sql-notify-title" linkend="sql-notify">
|
1999-07-14 22:32:59 +02:00
|
|
|
contains a more extensive
|
|
|
|
discussion of the use of <command>LISTEN</command> and
|
|
|
|
<command>NOTIFY</command>.
|
|
|
|
</para>
|
2003-04-27 01:56:51 +02:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Parameters</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="PARAMETER">name</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Name of a notification (any identifier).
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>*</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
All current listen registrations for this session are cleared.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
|
|
|
|
<para>
|
Update reference documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 00:26:05 +01:00
|
|
|
You can unlisten something you were not listening for; no warning or error
|
2003-09-09 20:28:53 +02:00
|
|
|
will appear.
|
2003-04-27 01:56:51 +02:00
|
|
|
</para>
|
1999-07-14 22:32:59 +02:00
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<para>
|
2003-09-09 20:28:53 +02:00
|
|
|
At the end of each session, <command>UNLISTEN *</command> is
|
2003-04-27 01:56:51 +02:00
|
|
|
automatically executed.
|
|
|
|
</para>
|
1999-07-14 22:32:59 +02:00
|
|
|
</refsect1>
|
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Examples</title>
|
1999-07-14 22:32:59 +02:00
|
|
|
|
|
|
|
<para>
|
2003-04-27 01:56:51 +02:00
|
|
|
To make a registration:
|
1999-07-14 22:32:59 +02:00
|
|
|
|
2000-03-26 20:32:30 +02:00
|
|
|
<programlisting>
|
2000-07-21 06:49:23 +02:00
|
|
|
LISTEN virtual;
|
|
|
|
NOTIFY virtual;
|
2003-09-13 01:04:46 +02:00
|
|
|
Asynchronous notification "virtual" received from server process with PID 8448.
|
2000-03-26 20:32:30 +02:00
|
|
|
</programlisting>
|
1999-07-14 22:32:59 +02:00
|
|
|
</para>
|
1998-10-21 07:34:12 +02:00
|
|
|
|
1999-07-14 22:32:59 +02:00
|
|
|
<para>
|
2003-09-13 01:04:46 +02:00
|
|
|
Once <command>UNLISTEN</> has been executed, further <command>NOTIFY</>
|
|
|
|
commands will be ignored:
|
1999-07-14 22:32:59 +02:00
|
|
|
|
2000-03-26 20:32:30 +02:00
|
|
|
<programlisting>
|
2000-07-21 06:48:33 +02:00
|
|
|
UNLISTEN virtual;
|
|
|
|
NOTIFY virtual;
|
2003-04-27 01:56:51 +02:00
|
|
|
-- no NOTIFY event is received
|
2000-03-26 20:32:30 +02:00
|
|
|
</programlisting>
|
1999-07-14 22:32:59 +02:00
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2003-04-27 01:56:51 +02:00
|
|
|
<refsect1>
|
|
|
|
<title>Compatibility</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
There is no <command>UNLISTEN</command> command in the SQL standard.
|
|
|
|
</para>
|
1999-07-14 22:32:59 +02:00
|
|
|
</refsect1>
|
2003-09-15 05:21:51 +02:00
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
|
|
|
<member><xref linkend="sql-listen" endterm="sql-listen-title"></member>
|
|
|
|
<member><xref linkend="sql-notify" endterm="sql-notify-title"></member>
|
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
1999-07-14 22:32:59 +02:00
|
|
|
</refentry>
|