Re: support for MERGE

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Daniel Westermann <dwe(at)dbi-services(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Subject: Re: support for MERGE
Date: 2022-01-13 09:51:33
Message-ID: 202201130951.sam572b7y5zn@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-Jan-12, Andrew Dunstan wrote:

> The problem with patches like this is that they seriously screw up the
> cfbot, which doesn't know about the previous patches you want this based
> on top of. See <>

Here's a v5 that includes Simon's changes.

Álvaro Herrera PostgreSQL Developer —

Attachment Content-Type Size
v5-0001-MERGE-SQL-Command-following-SQL-2016.patch text/x-diff 393.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Borisov 2022-01-13 09:53:23 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Previous Message Pavel Stehule 2022-01-13 09:48:01 Re: Add Boolean node