Date: Tue, 15 Sep 2020 21:26:39 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>,
	pgsql-bugs@lists.postgresql.org
Subject: Re: [BUG v13] Crash with event trigger in extension
Message-ID: <20200916002639.GA21403@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200912002149.GK2743@paquier.xyz>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2020-Sep-12, Michael Paquier wrote:

> On Fri, Sep 11, 2020 at 10:09:00AM +0200, Jehan-Guillaume de Rorthais wrote:
> > On Fri, 11 Sep 2020 15:14:41 +0900 Michael Paquier <michael@paquier.xyz> wrote:
> >> FWIW, I think that the fix proposed is fine as-is, and that we had
> >> better apply it.
> > 
> > +1
> 
> Alvaro, would you prefer doing the final checks on this patch by
> yourself and potentially commit it?

I gave this a very long look and was convinced that it was going to
break with multi-statement query strings, but it turns out that it
wasn't.  So I pushed it without any other changes.

I forgot to add reviewer credit to the commit message :-(  My apologies

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services