And some UNLISTEN doco too!

diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml
new file mode 100644 (file)
index 0000000..1fa0083
--- /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
+
+</div>
<div class="diff add">+Inputs</div>
<div class="diff add">+
+
+
+
+
+
+notifyname
+
+
+
+Name of notify condition to stop listening to.
+If "*", all current listen registrations for this backend are cleared.
+
+
+
+
+
+
+
+1998-10-07
+
+</div>
<div class="diff add">+Outputs</div>
<div class="diff add">+
+
+
+
+
+
+status
+
+
+
+
+
+
+UNLISTEN
+
+
+
+Acknowledgement that statement has executed.
+
+
+
+
+
+
+
+
+
+
+
+
+1998-10-07
+
+</div>
<div class="diff add">+Description</div>
<div class="diff add">+
+
+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.
+
+
+</div>
<div class="diff add">+Usage</div>
<div class="diff add">+
+
+
+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=>
+
+
+
+
+
+</div>
<div class="diff add">+Compatibility</div>
<div class="diff add">+
+
+
+
+
+1998-10-07
+
+</div>
<div class="diff add">+SQL92</div>
<div class="diff add">+
+
+   There is no UNLISTEN in SQL92.
+