Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date
Msg-id aSJEgABrlp7CyBJQ@paquier.xyz
Whole thread Raw
In response to Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
List pgsql-hackers
On Sat, Nov 22, 2025 at 03:16:44PM +0100, Alvaro Herrera wrote:
>         ExecDropSingleTupleTableSlot(existing_slot);
> +       INJECTION_POINT("check-exclusion-or-unique-constraint-no-conflict", &conflict);
>
> However, I don't see that the SQL injection point interface has the
> ability to receive arguments, so I'm guessing that this is not workable?
> Maybe something to consider for the future.

Are you referring to something like 371f2db8b05e here?  This has been
added in 18.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: Add notification on BEGIN ATOMIC SQL functions using temp relations
Next
From: Michael Paquier
Date:
Subject: Re: Remove unused fields from BufferCacheNumaRec