| From: | Zhihong Yu <zyu(at)yugabyte(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(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-14 00:15:45 |
| Message-ID: | CALNJ-vSjsyxagT2SdXsiAjd_L55x+RfT9iBavGVTpprSaxkQ-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 13, 2022 at 4:43 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> Apologies, there was a merge failure and I failed to notice. Here's the
> correct patch.
>
> (This is also in github.com/alvherre/postgres/tree/merge-15)
>
> Hi,
For v6-0001-MERGE-SQL-Command-following-SQL-2016.patch :
+ * Either we were dealing with a NOT MATCHED tuple or
+ * ExecMergeNotMatched() returned "false", indicating the previously
I think there was a typo above: ExecMergeMatched() returned "false"
because ExecMergeMatched() is called above the comment.
Cheers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-01-14 00:18:07 | Re: row filtering for logical replication |
| Previous Message | Justin Pryzby | 2022-01-13 23:58:27 | Re: libpq compression (part 2) |