From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Daniel Westermann <dwe(at)dbi-services(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: support for MERGE |
Date: | 2022-08-01 14:52:57 |
Message-ID: | 20220801145257.GA15006@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 14, 2022 at 11:27:06AM +0200, Álvaro Herrera wrote:
> @@ -448,9 +448,9 @@ COMMIT;
> and execute the first one that succeeds.
> If <command>MERGE</command> attempts an <command>INSERT</command>
> and a unique index is present and a duplicate row is concurrently
> - inserted, then a uniqueness violation is raised.
> - <command>MERGE</command> does not attempt to avoid the
> - error by executing an <command>UPDATE</command>.
> + inserted, then a uniqueness violation error is raised;
> + <command>MERGE</command> does not attempt to avoid such
> + errors by evaluating <literal>MATCHED</literal> conditions.
This was a portion of a chang that was committed as ffffeebf2.
But I don't understand why this changed from "does not attempt to avoid the
error by executing an <command>UPDATE</command>." to "...by evaluating
<literal>MATCHED</literal> conditions."
Maybe it means to say "..by re-starting evaluation of match conditions".
Sorry to re-raise this 6 weeks later..
--
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Dong Wook Lee | 2022-08-01 14:53:35 | Re: Add test of pg_prewarm extenion |
Previous Message | Japin Li | 2022-08-01 14:42:22 | Re: Typo in pg_db_role_setting.h |