Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY

On 2025-Nov-23, Michael Paquier wrote:

> 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.

Yes, exactly that ... but can this be used by the SQL injection points
functionality? The test is an isolation .spec file, and I didn't find a
way to say "make me sleep when I hit this injection point, but only if
conflict is false". Or maybe I just missed it.

Thanks!

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Estoy de acuerdo contigo en que la verdad absoluta no existe...
El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)