Re: pgsql: New files for MERGE

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: New files for MERGE
Date: 2018-04-05 10:09:31
Message-ID: CA+TgmoYRJU5i-FDsX+0vcUkd-+K+9CRmBqheUCiNXJWUh3CnQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Apr 4, 2018 at 3:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, what's on the table is reverting this patch and asking you to try
> again in the v12 cycle. Given Andres' concerns about the executor design,
> and mine about the way the parsing end is built, there's certainly no way
> that that's all getting fixed by Saturday. Given pretty much everybody's
> unhappiness with the way this patch was forced through at the last minute,
> I do not think you should expect that we'll say, "okay, we'll let you ship
> a bad version of MERGE because there's no more time in this cycle".

+1.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2018-04-05 10:15:20 Re: pgsql: New files for MERGE
Previous Message Teodor Sigaev 2018-04-05 10:06:47 pgsql: Fix misprint in documentation

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2018-04-05 10:15:20 Re: pgsql: New files for MERGE
Previous Message Tomas Vondra 2018-04-05 09:33:00 Re: Online enabling of checksums