Re: Segfault when creating partition with a primary key and sql_drop trigger exists
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, "Jonathan S. Katz" <jkatz@postgresql.org>, Andres Freund <andres@anarazel.de>, Dmitry Dolgov <9erthalion6@gmail.com>, Marco Slot <marco@citusdata.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Onder Kalaci <onder@citusdata.com>
Date: 2018-10-05T23:54:54Z
Lists: pgsql-hackers
On Fri, Oct 05, 2018 at 04:04:02PM -0400, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.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. I have to admit that I am not confident enough to commit this patch myself yet as I would need to spend a couple of extra hours on it and looking at the event triggers generated for other event types, and there is a three-day weekend waiting ahead in Japan. Could any of you take care of it? -- Michael
Commits
-
Fix event triggers for partitioned tables
- b2f266f58d4c 9.6.11 landed
- ad08006ba037 12.0 landed
- a2a5159ed678 9.5.15 landed
- 1a852f7c1e27 11.0 landed
- 101b21ead356 10.6 landed