| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Possible G2-item at SERIALIZABLE |
| Date: | 2026-08-26 21:33:28 |
| Message-ID: | CAN4CZFPsCjExDMdMaPXMDwnRZiyY=0ybL963xu8Z6RWvjqOLjA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> One test does not quite prove what its comment says. The "next read
> re-reports" permutation repeats the same conflicting SELECT. The old
> code raises another serialization failure there too, by rediscovering
> the same dangerous structure rather than by noticing DOOMED. Could we
> use an unrelated third row for that read? It should succeed without
> the patch and fail immediately with it. The subsequent-write case
> already distinguishes the two versions.
You are right, that was indeed not a good test case. I fixed it in v3
with your suggestion, it is otherwise unchanged.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Doom-the-serializable-transaction-before-raising-.patch | application/octet-stream | 20.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | surya poondla | 2026-08-26 22:02:00 | Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work |
| Previous Message | Alexander Korotkov | 2026-08-26 16:42:22 | Re: MERGE/SPLIT PARTITIONS issues/questions |