Re: Segfault when creating partition with a primary key and sql_droptrigger exists - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Segfault when creating partition with a primary key and sql_droptrigger exists
Date
Msg-id 20180928031700.GE1500@paquier.xyz
Whole thread Raw
In response to Re: Segfault when creating partition with a primary key and sql_droptrigger exists  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: Segfault when creating partition with a primary key and sql_droptrigger exists  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, Sep 27, 2018 at 11:02:06PM +0200, Dmitry Dolgov wrote:
> Yes, you're right. Although probably it's not great that the sequence of
> EventTriggerAlterTableStart, EventTriggerAlterTableRelid and
> EventTriggerAlterTableEnd is distributed between different functions (which
> most likely is worth a comment in AlterTableInternal), but it's a minor
> concern.

I think that Alvaro should definitely look at this patch to be sure, or
I could do it, but I would need to spend way more time on this and check
event trigger interactions.

Anyway, I was struggling a bit regarding the location where adding a
regression test.  event_trigger.sql makes the most sense but in tests
for drops the objects are created before the event trigger is defined,
so that would need to move around so as the original problem is
reproducible.  Perhaps you have an idea for that?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: heap_sync seems rather oblivious to partitioned tables(wal_level=minimal)
Next
From: Michael Paquier
Date:
Subject: Use durable_unlink for .ready and .done files for WAL segment removal