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

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

> The apply-worker crash is still unfixed in master and 18/19 branches.
> Are there any remaining objections to the InvalidSnapshot guard?

Not from me, I attached a version using that upthread in[1]

[1]: https://www.postgresql.org/message-id/CAN4CZFPzwmTjbsu_hVu2bFENCssmycf4d1etjOn%3DmNq7dHwcoQ%40mail.gmail.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2026-11-04 19:53:30 Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Previous Message shihao zhong 2026-11-04 19:17:39 Re: Preferred way to submit a very large batch of bugs?