Re: [BUG]: segfault during update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUG]: segfault during update
Date: 2020-11-08 17:18:19
Message-ID: 1831655.1604855899@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Drouvot, Bertrand" <bdrouvot(at)amazon(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-11-08 17:46:44 Re: [BUG]: segfault during update
Previous Message Drouvot, Bertrand 2020-11-08 16:30:15 [BUG]: segfault during update