From: Tom Lane <tgl@sss.pgh.pa.us>
To: Drouvot, Bertrand <bdrouvot@amazon.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [BUG]: segfault during update
Date: Sun, 08 Nov 2020 12:18:19 -0500
Message-ID: <1831655.1604855899@sss.pgh.pa.us> (raw)
In-Reply-To: <db5d97c8-f48a-51e2-7b08-b73d5434d425@amazon.com>
References: <db5d97c8-f48a-51e2-7b08-b73d5434d425@amazon.com>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bdrouvot@amazon.com
Subject: Re: [BUG]: segfault during update
In-Reply-To: <1831655.1604855899@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox