From 69bdfc4090816d77a3d08684a30bfb05f8b1e104 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Wed, 3 Aug 2016 12:29:15 -0400
Subject: [PATCH] doc: Change recommendation to put NOTIFY into a rule
Suggest a statement trigger instead.
---
doc/src/sgml/ref/notify.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
index 4dd560838b1..3389aa055ca 100644
--- a/doc/src/sgml/ref/notify.sgml
+++ b/doc/src/sgml/ref/notify.sgml
@@ -68,7 +68,7 @@ NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
<para>
When <command>NOTIFY</command> is used to signal the occurrence of changes
to a particular table, a useful programming technique is to put the
- <command>NOTIFY</command> in a rule that is triggered by table updates.
+ <command>NOTIFY</command> in a statement trigger that is triggered by table updates.
In this way, notification happens automatically when the table is changed,
and the application programmer cannot accidentally forget to do it.
</para>
--
GitLab