From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Dmitry Igrishin <dmitigr(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: 36.1 Overview of Trigger Behavior |
Date: | 2016-04-29 17:07:29 |
Message-ID: | 572394D1.2020502@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-04-29 17:22:37 | Re: 36.2 Visibility of Data Changes |
Previous Message | Andrei M. Eichler | 2016-04-29 16:30:07 | Re: COPY options |