Re: Fwd: Problem with a "complex" upsert - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Fwd: Problem with a "complex" upsert
Date
Msg-id 8968.1533337119@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fwd: Problem with a "complex" upsert  (Andres Freund <andres@anarazel.de>)
Responses Re: Fwd: Problem with a "complex" upsert  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Andres Freund <andres@anarazel.de> writes:
> On 2018-08-03 18:32:57 -0400, Tom Lane wrote:
>> Balance the risks of shipping a broken release vs. waiting one
>> more quarter to ship the fix.  After a quick look at the size
>> of the patch, my own inclination if I were the committer would
>> be to wait till after the releases are out.  Or you might
>> consider pushing only to 11+HEAD, with the expectation of
>> back-patching later after we've gotten some beta results.

> This results in clearly inserting wrong data and/or crashing the
> server. And it's not a huge effect outside of already broken scenarios.
> I think we definitely should try to get this in.

Well, if you're excited about it, help Dean review it.  My own feeling
is that this case has been broken for several years with no one noticing,
so it can't be all that critical.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Range partition creation failing due to incorrectly decidinglower bound greater than upper
Next
From: Peter Geoghegan
Date:
Subject: Re: Fwd: Problem with a "complex" upsert