Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-docs-owner+M8761=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
	id 1bUdQL-000661-Mr
	for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2016 17:24:13 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-docs-owner+M8761=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
	id 1bUdQL-0002b0-4w
	for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2016 17:24:13 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <peter.eisentraut@2ndquadrant.com>)
	id 1bUdPy-0001iU-K2
	for pgsql-docs@postgresql.org; Tue, 02 Aug 2016 17:23:50 +0000
Received: from out5-smtp.messagingengine.com ([66.111.4.29])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <peter.eisentraut@2ndquadrant.com>)
	id 1bUdPv-0004qN-Iw
	for pgsql-docs@postgresql.org; Tue, 02 Aug 2016 17:23:49 +0000
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
	by mailout.nyi.internal (Postfix) with ESMTP id 338F120953
	for <pgsql-docs@postgresql.org>; Tue,  2 Aug 2016 13:23:46 -0400 (EDT)
Received: from frontend2 ([10.202.2.161])
  by compute2.internal (MEProxy); Tue, 02 Aug 2016 13:23:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:message-id:mime-version:subject:to:x-sasl-enc
	:x-sasl-enc; s=smtpout; bh=jhiRIh3N7QAKF/KAwPU3IZURAME=; b=C39OD
	vaLsz06dKLWyv+1aM5CZrP4tIhiCdwRA6cdRMGKmJIYPSwVsBuMWqhS42w3v3HAd
	kcq/1mapvJoQuWaxMHU1oc+OZ4xuAbr8aJ8REG9LSoV8vhHGopXlNnX8CXpEC/Pe
	g6Qg0vsKDvfDOZXED7MbstrVRlpf1UuTuQyunM=
X-Sasl-enc: swm528zfoptIA23iY7GjZJZAOz3AvzdOlq3uLi0DXOHD 1470158625
Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39])
	by mail.messagingengine.com (Postfix) with ESMTPA id ECEA4CCD81
	for <pgsql-docs@postgresql.org>; Tue,  2 Aug 2016 13:23:45 -0400 (EDT)
To: pgsql-docs <pgsql-docs@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: NOTIFY man page still recommends rules
Organization: 2ndQuadrant
Message-ID: <913aa238-04c7-a75f-28e6-8845119eb3df@2ndquadrant.com>
Date: Tue, 2 Aug 2016 13:23:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.6 (--)
List-Archive: <http://archives.postgresql.org/pgsql-docs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-docs.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@postgresql.org>
List-Post: <mailto:pgsql-docs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-docs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
X-Mailing-List: pgsql-docs
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

The NOTIFY man page writes

   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.

Is using rules here still best practice?  This was probably written
before statement triggers were available.

Even if yes, we might want to explain why, since we generally discourage
rule use otherwise.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs