Re: pgsql: New files for MERGE - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: pgsql: New files for MERGE
Date
Msg-id CABOikdNw9z0V+4TSS1B-jevdh3-mH1H8G3y7z+w+FYViiiP21w@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: New files for MERGE  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: New files for MERGE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Thu, Apr 5, 2018 at 12:16 AM, Andres Freund <andres@anarazel.de> wrote:
Hi,

On 2018-04-05 00:02:06 +0530, Pavan Deolasee wrote:
> Apologies from my end. Simon checked with me regarding your referenced
> email. I was in the middle of responding to it (with a add-on patch to take
> care of your review comments), but got side tracked by some high priority
> customer escalation. I shall respond soon.

Hows that an explanation for just going ahead and committing? Without
even commenting on why one thinks the pointed out issues are something
that can be resolved later or somesuch?  This has an incredibly rushed
feel to it.

While I don't want to answer that on Simon's behalf, my feeling is that he may not seen your email since it came pretty late. He had probably planned to commit the patch again first thing in the morning with the fixes I'd sent.

Anyways, I think your reviews comments are useful and I've incorporated most of those. Obviously certain things like creating a complete new executor machinery is not practical given where we're in the release cycle and I am not sure if that has any significant advantages over what we have today.

Thanks,
Pavan

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: Postgres stucks in deadlock detection
Next
From: Andres Freund
Date:
Subject: Re: Postgres stucks in deadlock detection