Request a Demo
Home   >   mailing lists

Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date
Msg-id CAEZATCVa3w1_eCRc376OB6u_92vrg3jnCwi4bvYHRt_Lak15Vg@mail.gmail.com
Whole thread
In response to Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row  (Zsolt Parragi <zsolt.parragi@percona.com>)
Responses Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
List pgsql-hackers
Tree view 
On Wed, 23 Sept 2026 at 13:51, Zsolt Parragi <zsolt.parragi@percona.com> wrote:
>
> On Wed, 23 Sep 2026, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> > I'm thinking now that making ExecCheckIndexConstraints() require
> > estate->es_snapshot was actually an unintended change of the kind that
> > probably wasn't safe for back-patching, because it might affect
> > extension code.
>
> I forgot to mention this, but the issue I mentioned only exists in 18
> and 19, earlier branches are not affected (at least without
> extensions).

Grepping on PGXN, I see no use of ExecCheckIndexConstraints(), so it's
probably your fix is OK.

Regards,
Dean

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Adding a range check on the sequence index from the publisher.
Next
From: Andrew Dunstan
Date:
Subject: Re: 64-bit MultiXactOffset vs. 9.3->9.4 upgrade, pg_resetwal, "wraparound" msg