Subject: Re: 36.2 Visibility of Data Changes
To: Dmitry Igrishin <dmitigr@gmail.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
References: 
 <CAAfz9KNpv8HtYDNJ4T1e94h4WUhyGXxVd3dnNuo=rSyXCt1sRA@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <5723985D.2050809@2ndquadrant.com>
Date: Fri, 29 Apr 2016 13:22:37 -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: 
 <CAAfz9KNpv8HtYDNJ4T1e94h4WUhyGXxVd3dnNuo=rSyXCt1sRA@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 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


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