Subject: Re: 36.1 Overview of Trigger Behavior
To: Dmitry Igrishin <dmitigr@gmail.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
References: 
 <CAAfz9KNqLXAkygKatsTZTopNhKaCKfLiGkhrqTvEuP-OW_dtRg@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <572394D1.2020502@2ndquadrant.com>
Date: Fri, 29 Apr 2016 13:07:29 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101
 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: 
 <CAAfz9KNqLXAkygKatsTZTopNhKaCKfLiGkhrqTvEuP-OW_dtRg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On 08/11/2015 05:51 AM, Dmitry Igrishin wrote:
> Subparagraph 8:
> I suggest to replace
> "BEFORE row-level triggers to execute"
> with
> "row-level BEFORE triggers to execute"
> for consistency.

Fixed that one.  Wasn't so sure about the one below.

> 
> 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."

-- 
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