Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date: 2025-11-22 23:17:20
Message-ID: aSJEgABrlp7CyBJQ@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-11-22 23:23:22 Re: Remove unused fields from BufferCacheNumaRec
Previous Message Jim Jones 2025-11-22 23:09:03 Re: Add notification on BEGIN ATOMIC SQL functions using temp relations