Re: Segfault when creating partition with a primary key and sql_drop trigger exists

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Marco Slot <marco(at)citusdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Onder Kalaci <onder(at)citusdata(dot)com>
Subject: Re: Segfault when creating partition with a primary key and sql_drop trigger exists
Date: 2018-10-05 20:04:02
Message-ID: 2026.1538769842@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2018-Oct-04, Tom Lane wrote:
>> Not sure about that. Alvaro seems to think there's a generic problem
>> in event trigger processing, which if true, was likely there pre-v11.

> After sleeping on this, I think that a better answer is to fix the crash
> per Michael's proposed patch, and fix the rest of the deparse problem
> later.

Well, let's push it sooner not later, so we can get buildfarm coverage
before RC1.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-10-05 20:06:15 Re: Odd 9.4, 9.3 buildfarm failure on s390x
Previous Message Alvaro Herrera 2018-10-05 19:57:59 Re: Segfault when creating partition with a primary key and sql_drop trigger exists