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

From Alvaro Herrera
Subject Re: Segfault when creating partition with a primary key and sql_droptrigger exists
Date
Msg-id 20181005195759.l2viv7sbgczsybyh@alvherre.pgsql
Whole thread Raw
In response to Re: Segfault when creating partition with a primary key and sql_drop trigger exists  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Segfault when creating partition with a primary key and sql_drop trigger exists  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-Oct-04, Tom Lane wrote:

> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
> > On 10/4/18 8:34 PM, Michael Paquier wrote:
> >> I am suggesting to fix the issue after RC1 is released, but before GA.
> 
> > That approach would mean we would require an RC2, which would further
> > delay the GA.
> 
> 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.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: Segfault when creating partition with a primary key and sql_droptrigger exists
Next
From: Tom Lane
Date:
Subject: Re: Segfault when creating partition with a primary key and sql_drop trigger exists