Re: [BUG v13] Crash with event trigger in extension - Mailing list pgsql-bugs

From Jehan-Guillaume de Rorthais
Subject Re: [BUG v13] Crash with event trigger in extension
Date
Msg-id 20200903194114.34af669a@firost
Whole thread Raw
In response to Re: [BUG v13] Crash with event trigger in extension  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Wed, 2 Sep 2020 13:53:28 -0400
Alvaro Herrera <alvherre@2ndquadrant.com> wrote:

> On 2020-Sep-02, Jehan-Guillaume de Rorthais wrote:
> 
> > Hi,
> > 
> > Philippe Beaudoin reported to me a crash he was able to reproduce with some
> > extension update script. Please, find in attachment a script that triggers
> > it. Just edit the three first vars to point to a temporary installation and
> > instance.
> > 
> > Some git bisect shows the bug was introduced by b5810de3f4, where
> > multi-statement query strings are using different short memory contexts.
> 
> Good find.
> 
> I think we should turn your case into a proper TAP test so that we can
> incorporate it, for coverage -- the lines you patch do appear covered,
> but obviously not in these specific conditions.  I'm just not very sure
> *where* to add it; maybe src/test/modules/test_extensions is the place
> to have it, though that one doesn't have TAP tests currently.  An easy
> addition, though.

Sure, please find in attachment patch v2 adding a regression test.

Regards,

Attachment

pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #16606: V 4.25: unable to drop database
Next
From: Tom Lane
Date:
Subject: ...