dblink_get_notify(3) [centos man page]

DBLINK_GET_NOTIFY(3)					  PostgreSQL 9.2.7 Documentation				      DBLINK_GET_NOTIFY(3)

NAME

       dblink_get_notify - retrieve async notifications on a connection

SYNOPSIS

       dblink_get_notify() returns setof (notify_name text, be_pid int, extra text)
       dblink_get_notify(text connname) returns setof (notify_name text, be_pid int, extra text)

DESCRIPTION

       dblink_get_notify retrieves notifications on either the unnamed connection, or on a named connection if specified. To receive notifications
       via dblink, LISTEN must first be issued, using dblink_exec. For details see LISTEN(7) and NOTIFY(7).

ARGUMENTS

       conname
	   The name of a named connection to get notifications on.

RETURN VALUE

       Returns setof (notify_name text, be_pid int, extra text), or an empty set if none.

EXAMPLES

	   SELECT dblink_exec('LISTEN virtual');
	    dblink_exec
	   -------------
	    LISTEN
	   (1 row)

	   SELECT * FROM dblink_get_notify();
	    notify_name | be_pid | extra
	   -------------+--------+-------
	   (0 rows)

	   NOTIFY virtual;
	   NOTIFY

	   SELECT * FROM dblink_get_notify();
	    notify_name | be_pid | extra
	   -------------+--------+-------
	    virtual	|   1229 |
	   (1 row)

PostgreSQL 9.2.7						    2014-02-17						      DBLINK_GET_NOTIFY(3)

LISTEN(7)						  PostgreSQL 9.2.7 Documentation						 LISTEN(7)

NAME

       LISTEN - listen for a notification

SYNOPSIS

       LISTEN channel

DESCRIPTION

       LISTEN registers the current session as a listener on the notification channel named channel. If the current session is already registered
       as a listener for this notification channel, nothing is done.

       Whenever the command NOTIFY channel is invoked, either by this session or another one connected to the same database, all the sessions
       currently listening on that notification channel are notified, and each will in turn notify its connected client application.

       A session can be unregistered for a given notification channel with the UNLISTEN command. A session's listen registrations are
       automatically cleared when the session ends.

       The method a client application must use to detect notification events depends on which PostgreSQL application programming interface it
       uses. With the libpq library, the application issues LISTEN as an ordinary SQL command, and then must periodically call the function
       PQnotifies to find out whether any notification events have been received. Other interfaces such as libpgtcl provide higher-level methods
       for handling notify events; indeed, with libpgtcl the application programmer should not even issue LISTEN or UNLISTEN directly. See the
       documentation for the interface you are using for more details.

       NOTIFY(7) contains a more extensive discussion of the use of LISTEN and NOTIFY.

PARAMETERS

       channel
	   Name of a notification channel (any identifier).

NOTES

       LISTEN takes effect at transaction commit. If LISTEN or UNLISTEN is executed within a transaction that later rolls back, the set of
       notification channels being listened to is unchanged.

       A transaction that has executed LISTEN cannot be prepared for two-phase commit.

EXAMPLES

       Configure and execute a listen/notify sequence from psql:

	   LISTEN virtual;
	   NOTIFY virtual;
	   Asynchronous notification "virtual" received from server process with PID 8448.

COMPATIBILITY

       There is no LISTEN statement in the SQL standard.

SEE ALSO

       NOTIFY(7), UNLISTEN(7)

PostgreSQL 9.2.7						    2014-02-17								 LISTEN(7)