Horton

Re: automatic restore point

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>, "Yotsunaga, Naoki" <yotsunaga.naoki@jp.fujitsu.com>, 'Postgres hackers' <pgsql-hackers@postgresql.org>
Date: 2018-10-10T21:09:23Z
Lists: pgsql-hackers 
On 05/10/2018 15:26, Peter Eisentraut wrote:
> It looked for a moment that
> 
>     isCompleteQuery = (context <= PROCESS_UTILITY_QUERY)
> 
> in ProcessUtilitySlow() might be a problem, since that omits
> PROCESS_UTILITY_QUERY_NONATOMIC, but it's not actually a problem, since
> the commands that run this way (CALL and SET from PL/pgSQL) don't have
> event triggers.  But anyway, I propose the attached patch to rephrase
> that.  Also some tests that show it all works as expected.

I have committed these to master.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Slightly correct context check for event triggers