Re: Fwd: Problem with a "complex" upsert

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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:32:57
Message-ID: 7664.1533335577@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-bugs

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.
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.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andres Freund 2018-08-03 22:44:55 Re: Fwd: Problem with a "complex" upsert
Previous Message Dean Rasheed 2018-08-03 21:26:11 Re: Fwd: Problem with a "complex" upsert

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-08-03 22:44:55 Re: Fwd: Problem with a "complex" upsert
Previous Message Dean Rasheed 2018-08-03 21:26:11 Re: Fwd: Problem with a "complex" upsert