support for MERGE

Ranier Vilela <ranier.vf@gmail.com>

From: Ranier Vilela <ranier.vf@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Justin Pryzby <pryzby@telsasoft.com>, amitlangote09@gmail.com, Japin Li <japinli@hotmail.com>, Zhihong Yu <zyu@yugabyte.com>, simon.riggs@enterprisedb.co, Tomas Vondra <tomas.vondra@enterprisedb.com>, dwe@dbi-services.com, er@xs4all.nl, Jaime Casanova <jcasanov@systemguards.com.ec>, Andres Freund <andres@anarazel.de>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2022-03-31T17:38:12Z
Lists: pgsql-hackers

Attachments

On 2022-Mar-28, Alvaro Herrera wrote:

>> I intend to get this pushed after lunch.

>Pushed, with one more change: fetching the tuple ID junk attribute in
>ExecMerge was not necessary, since we already had done that in
>ExecModifyTable. We just needed to pass that down to ExecMerge, and
>make sure to handle the case where there isn't one.
Hi,

I think that there is an oversight at 7103ebb
<https://github.com/postgres/postgres/commit/7103ebb7aae8ab8076b7e85f335ceb8fe799097c>
There is no chance of Assert preventing this bug.

regards,
Ranier Vilela

Commits

  1. adjust_partition_colnos mustn't be called if not needed

  2. Add support for MERGE SQL command