From ac5a8b9ab578843fc04b940fcb5562063ff9b5c7 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 8 Oct 1998 00:19:13 +0000 Subject: [PATCH] And some UNLISTEN doco too! --- doc/src/sgml/ref/unlisten.sgml | 144 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 144 insertions(+) create mode 100644 doc/src/sgml/ref/unlisten.sgml diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml new file mode 100644 index 0000000000..1fa0083e04 --- /dev/null +++ b/doc/src/sgml/ref/unlisten.sgml @@ -0,0 +1,144 @@ + + + +UNLISTEN + +SQL - Language Statements + + + +UNLISTEN + + +Stop listening for notification on a notify condition + + + + +1998-10-07 + + +UNLISTEN notifyname | "*" + + + + +1998-10-07 + + +Inputs + + + + + + +notifyname + + + +Name of notify condition to stop listening to. +If "*", all current listen registrations for this backend are cleared. + + + + + + + +1998-10-07 + + +Outputs + + + + + + +status + + + + + + +UNLISTEN + + + +Acknowledgement that statement has executed. + + + + + + + + + + + + +1998-10-07 + + +Description + + +UNLISTEN cancels any existing registration of the current +Postgres backend as a listener on the notify +condition notifyname. +The special condition name "*" means to cancel all listener registrations +for the current backend. + + +The backend does not complain if you UNLISTEN something you were not +listening for. + + +Each backend will automatically execute UNLISTEN "*" when +exiting. + + +The reference page for NOTIFY contains a more extensive +discussion of the use of LISTEN and +NOTIFY. + + + +Usage + + + +postgres=> listen virtual; +LISTEN +postgres=> notify virtual; +NOTIFY +ASYNC NOTIFY of 'virtual' from backend pid '12317' received +postgres=> unlisten virtual; +UNLISTEN +postgres=> notify virtual; +NOTIFY +-- notice no NOTIFY event is received +postgres=> + + + + + + +Compatibility + + + + + +1998-10-07 + + +SQL92 + + + There is no UNLISTEN in SQL92. + -- 2.11.0