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

From Dmitry Dolgov
Subject Re: Segfault when creating partition with a primary key and sql_droptrigger exists
Date
Msg-id CA+q6zcX9F8qDEuhToQhorYkZtqCm+Z+qR=PaFrsvJ9EOg2eLPA@mail.gmail.com
Whole thread Raw
In response to Re: Segfault when creating partition with a primary key and sql_droptrigger exists  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Segfault when creating partition with a primary key and sql_droptrigger exists  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> On Mon, 24 Sep 2018 at 17:58, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
> On 2018-Sep-20, Marco Slot wrote:
>
> > We're seeing a segmentation fault when creating a partition of a
> > partitioned table with a primary key when there is a sql_drop trigger on
> > Postgres 11beta4.
> >
> > We discovered it because the Citus extension creates a sql_drop trigger,
> > but it's otherwise unrelated to the Citus extension:
> > https://github.com/citusdata/citus/issues/2390
>
> Thanks for the reproducer.  Will research.

Shouldn't it be fixed by adding EventTriggerAlterTableStart? Judging from the
following call of ATController, we can just pass NULL as parsetree.

Attachment

pgsql-hackers by date:

Previous
From: "Iwata, Aya"
Date:
Subject: RE: libpq debug log
Next
From: Arthur Zakirov
Date:
Subject: Re: PATCH: Update snowball stemmers