From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Mario De Frutos Dieguez <mariodefrutos(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Fwd: Problem with a "complex" upsert |
Date: | 2018-08-03 22:44:55 |
Message-ID: | 20180803224455.4g2hnvciynu2s7iv@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-bugs |
On 2018-08-03 18:32:57 -0400, Tom Lane wrote:
> Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> > On 3 August 2018 at 19:46, Andres Freund <andres(at)anarazel(dot)de> wrote:
> >> Are you planning to push a version of this soon? It'd be good to
> >> get this included in the next set of releases...
>
> > Yes, agreed. I'll try to do it this weekend.
>
> Keep in mind that we are hard up against the release deadline.
Right.
> This is a bad weekend to be pushing anything you are not 100.00%
> sure of; the later, the more so, as by Sunday you will probably not
> get a complete set of buildfarm reports before the wrap happens.
>
> 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.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-08-03 22:58:39 | Re: Fwd: Problem with a "complex" upsert |
Previous Message | Tom Lane | 2018-08-03 22:32:57 | Re: Fwd: Problem with a "complex" upsert |
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2018-08-03 22:54:52 | Range partition creation failing due to incorrectly deciding lower bound greater than upper |
Previous Message | Tom Lane | 2018-08-03 22:32:57 | Re: Fwd: Problem with a "complex" upsert |