Re: pgsql: New files for MERGE

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: New files for MERGE
Date: 2018-04-04 18:53:56
Message-ID: CAH2-WzkONmtbV4+cGuGrP3fos13NT0KcRimwLNNObM1dfZkApw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Apr 4, 2018 at 11:46 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> 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.

I agree that this was handled in a way that was just unsatisfactory.
It was also unnecessary, since we still have a few days left until
feature freeze.

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Pavan Deolasee 2018-04-04 18:55:27 Re: pgsql: New files for MERGE
Previous Message Andres Freund 2018-04-04 18:46:32 Re: pgsql: New files for MERGE

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2018-04-04 18:55:10 Re: Postgres stucks in deadlock detection
Previous Message Tom Lane 2018-04-04 18:50:12 Re: BUG #14999: pg_rewind corrupts control file global/pg_control