Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-docs-owner+M8337=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1ZP6Dj-0003Ne-Jo
 for pgsql-docs@arkaria.postgresql.org; Tue, 11 Aug 2015 09:51:47 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.84) (envelope-from
 <pgsql-docs-owner+M8337=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1ZP6Di-00058Q-TG
 for pgsql-docs@arkaria.postgresql.org; Tue, 11 Aug 2015 09:51:46 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <dmitigr@gmail.com>) id 1ZP6DO-0004lT-Pf
 for pgsql-docs@postgresql.org; Tue, 11 Aug 2015 09:51:26 +0000
Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c])
 by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
 (Exim 4.84) (envelope-from <dmitigr@gmail.com>) id 1ZP6DH-000734-DK
 for pgsql-docs@postgresql.org; Tue, 11 Aug 2015 09:51:26 +0000
Received: by iodt126 with SMTP id t126so5299090iod.2
 for <pgsql-docs@postgresql.org>; Tue, 11 Aug 2015 02:51:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=krWbCtYTJOIIvUonOQcJEOWPNsVtAfUMvPV0kxalAis=;
 b=MuL3tJzZmYINzLZo9woU1sUdbkvyYBR32SNVjvuviLqQqvUsWFvE88UXvXRK16ylRq
 mlgl1+dSzisMVS2sJ0dwT71t5qlXIH5e2CQvXMl4WaNH/0J32Z8Forxy2tUVolcxedjQ
 qdPD+8FIRN6Hl6tAOMFYz4nIPToY6LgWklzyPXsj0zfur8wNdEzWeUeDsas3BE9UBGmz
 POTt96dIObtkB+jINjqBdGdrKKHGafsEOx6skKjFWaatHU7J36u9bQPxlp6LmPvzuUDg
 ge2PURpDYMJMwji0y6Gamf+7h0bi59LNa7Sr+LOIqClpX+tD6aJiDHIkD6UMnQYsxMc7
 CKhw==
MIME-Version: 1.0
X-Received: by 10.107.10.144 with SMTP id 16mr31595203iok.43.1439286677335;
 Tue, 11 Aug 2015 02:51:17 -0700 (PDT)
Received: by 10.79.111.196 with HTTP; Tue, 11 Aug 2015 02:51:17 -0700 (PDT)
Date: Tue, 11 Aug 2015 12:51:17 +0300
Message-ID: 
 <CAAfz9KNqLXAkygKatsTZTopNhKaCKfLiGkhrqTvEuP-OW_dtRg@mail.gmail.com>
Subject: 36.1 Overview of Trigger Behavior
From: Dmitry Igrishin <dmitigr@gmail.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: multipart/alternative; boundary=001a113f940e21f689051d060b91
X-Pg-Spam-Score: -2.7 (--)
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

--001a113f940e21f689051d060b91
Content-Type: text/plain; charset=UTF-8

Subparagraph 8:
I suggest to replace
"BEFORE row-level triggers to execute"
with
"row-level BEFORE triggers to execute"
for consistency.

Subparagraph 14:
While WHEN can be used with INSERT too, I suggest to replace
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row update occurs, and it determines
whether an event is queued to fire the trigger at the end of
statement."
with
"However, in an AFTER trigger, the WHEN condition is
evaluated just after the row inserted or updated, and it determines
whether an event is queued to fire the trigger at the end of
statement."

-- 
// Dmitry.

--001a113f940e21f689051d060b91
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Subparagraph 8:<div>I suggest to replace<br><div>&quot;BEF=
ORE row-level triggers to execute&quot;</div><div>with</div><div>&quot;row-=
level BEFORE triggers to execute&quot;</div><div>for consistency.</div><div=
><br></div><div>Subparagraph 14:</div><div>While WHEN can be used with INSE=
RT too, I suggest to replace<br></div><div>&quot;However, in an AFTER trigg=
er, the WHEN condition is</div><div>evaluated just after the row update occ=
urs, and it determines</div><div>whether an event is queued to fire the tri=
gger at the end of</div><div>statement.&quot;</div><div>with</div><div><div=
>&quot;However, in an AFTER trigger, the WHEN condition is</div><div>evalua=
ted just after the row inserted or updated, and it determines</div><div>whe=
ther an event is queued to fire the trigger at the end of</div><div>stateme=
nt.&quot;</div></div><div><div><br></div>-- <br><div class=3D"gmail_signatu=
re"><div dir=3D"ltr"><div>// Dmitry.<br><br></div></div></div>
</div></div></div>

--001a113f940e21f689051d060b91--