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

From Jehan-Guillaume de Rorthais
Subject [BUG v13] Crash with event trigger in extension
Date
Msg-id 20200902193715.6e0269d4@firost
Whole thread Raw
Responses Re: [BUG v13] Crash with event trigger in extension  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
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.

To make it short, any ALTER TABLE command in an extension script is 
currently calling lappend to add its command to the
currentEventTriggerState->commandList list from its own short context instead
of using the context of currentEventTriggerState.

Because of this, when we call EventTriggerCollectSimpleCommand() for the top
level "ALTER EXTENSION" query, the list has long been removed and a new call of
lappend on currentEventTriggerState->commandList raise
Assert(IsPointerList(list)).

Please, find in attachement a bug fix proposal. I did a very quick look at
other ->commandList manipulations in event_trigger.c. They all appear to
be in the correct context in a first look.

Regards,

Attachment

pgsql-bugs by date:

Previous
From: Dave Cramer
Date:
Subject: Re: BUG #16557: getProcedureColumns() function returns columns, when there is no existing Stored Procedure in the DB
Next
From: Alvaro Herrera
Date:
Subject: Re: [BUG v13] Crash with event trigger in extension