| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | marco(at)citusdata(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, onder(at)citusdata(dot)com |
| Subject: | Re: Segfault when creating partition with a primary key and sql_drop trigger exists |
| Date: | 2018-09-25 11:39:59 |
| Message-ID: | CA+q6zcX9F8qDEuhToQhorYkZtqCm+Z+qR=PaFrsvJ9EOg2eLPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Mon, 24 Sep 2018 at 17:58, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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 | Content-Type | Size |
|---|---|---|
| sql_drop_on_partition.patch | application/octet-stream | 446 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2018-09-25 11:45:08 | Re: PATCH: Update snowball stemmers |
| Previous Message | Maxim Boguk | 2018-09-25 11:24:39 | Re: BUG #15160: planner overestimates number of rows in join when there are more than 200 rows coming from CTE |