| 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.2 Visibility of Data Changes |
| Date: | 2016-04-29 17:22:37 |
| Message-ID: | 5723985D.2050809@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 08/11/2015 06:18 AM, Dmitry Igrishin wrote:
> Subparagraph 1:
> I suggest to replace
> "Statement-level triggers follow simple visibility rules: none of the
> changes made by a statement are visible to statement-level
> triggers that are invoked before the statement, whereas all
> modifications are visible to statement-level AFTER triggers."
> with
> "Statement-level triggers follow simple visibility rules: none of the
> changes made by a statement are visible to statement-level
> BEFORE triggers, whereas all modifications are visible to
> statement-level AFTER triggers."
done
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2016-05-01 15:18:53 | Error in xindex.sgml |
| Previous Message | Peter Eisentraut | 2016-04-29 17:07:29 | Re: 36.1 Overview of Trigger Behavior |