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-03 12:14:48
Message-ID: CAEZATCXTo2iO0uHHp=yPA2daWeUyYTNRAfr0kxN15WKyySLtHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 30 Oct 2026 at 16:53, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> The apply-worker crash is still unfixed in master and 18/19 branches.
> Are there any remaining objections to the InvalidSnapshot guard?
>
> Minor releases are approachnig...

Thanks for the reminder. I'll take care of this using an InvalidSnapshot guard.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shlok Kyal 2026-11-03 12:37:19 Re: Per-table resync for logical replication subscriptions
Previous Message Narayanan Venkateswaran 2026-11-03 12:07:55 Re: Proposal: Conflict log history table for Logical Replication