Re: [BUG]: segfault during update - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [BUG]: segfault during update
Date
Msg-id 1831655.1604855899@sss.pgh.pa.us
Whole thread Raw
In response to [BUG]: segfault during update  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
Responses Re: [BUG]: segfault during update  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Drouvot, Bertrand" <bdrouvot@amazon.com> writes:
> Here is a scenario that produces segfault during update (on version 12 
> and 13):

Hm.  So the point about failing to reproduce dropped columns is more
critical than I thought.  I wonder how come we get away with that before
v12?

> So, we would need to back port this commit on 12 and 13.

Yeah, this is sufficient reason why we must use the more invasive
patch on those branches.  What I'm wondering now is if there's a
way to break even-older branches based on failure to handle dropped
columns here.

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: [BUG]: segfault during update
Next
From: Tom Lane
Date:
Subject: Re: [BUG]: segfault during update