| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Bryan Green <dbryan(dot)green(at)gmail(dot)com>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com> |
| Subject: | Re: serializable anomaly - duplicate primary keys |
| Date: | 2026-10-01 15:23:49 |
| Message-ID: | CAJ7c6TMSLKtuG8Wc7LJGo_TCCt3_6YoF8YTVaPURwOgVO3eY-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> This extends the table AM interface. An ABI-preserving back-branch fix can
> be considered separately.
Actually I think we should do just the opposite - focus on the patch
that can be backported and discuss possible improvements for the
`master` branch later.
The root cause is that unique checks use a dirty snapshot. They can
decide a key is unused because of a deletion the transaction cannot
see. The fix might be to ask our own snapshot the same question, and
fail if it still sees the key in use. I don't think this will require
an ABI change.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-10-01 15:26:34 | Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row |
| Previous Message | Jacob Champion | 2026-10-01 15:00:15 | Re: Commitfest PG20-2 is now closed |