Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, David Christensen <david+pg(at)pgguru(dot)net>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date: 2026-11-04 19:53:30
Message-ID: CAEZATCW+BYf8srDT4fbcW980nANJ5QYhuodjGdBktAZsVR5cQA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 3 Nov 2026 at 12:14, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>
> Thanks for the reminder. I'll take care of this using an InvalidSnapshot guard.

OK, I've pushed and back-patched that fix down to v14, so no extension
code will need changing.

I didn't bother with the test case, since it only applies to v18
onwards, and it didn't seem worth carrying that extra test code just
for this.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-11-04 20:16:10 Re: Fix cumulative WAL statistics double-counting from parallel workers
Previous Message Zsolt Parragi 2026-11-04 19:49:07 Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row