Re: Possible G2-item at SERIALIZABLE - Mailing list pgsql-bugs

From Andrey Borodin
Subject Re: Possible G2-item at SERIALIZABLE
Date
Msg-id 1F2F4318-437C-4AE1-8413-F94FBDD5AB68@yandex-team.ru
Whole thread
In response to Possible G2-item at SERIALIZABLE  (Kyle Kingsbury <aphyr@aphyr.com>)
Responses Re: Possible G2-item at SERIALIZABLE
List pgsql-bugs

> On 22 May 2026, at 21:44, Kyle Kingsbury <aphyr@aphyr.com> wrote:
>
> If y'all have any luck reproducing this, I'd love to hear about it!

It looks like I've reproduced something similar with savepoints on HEAD and
REL_18_STABLE. I can't tell if it's really all what you observe. But, probably, part of it.

If that error is raised inside a subtransaction, ROLLBACK TO SAVEPOINT swallows it
and the transaction is free to COMMIT, defeating serializable isolation.

I did not try beyond 18, but I think it always has been there.

PFA attached isolation tester and hand-wavy fix. But I suspect there are more G-items
around.

Full Jepsen test you proposed is currently tried by Nik's machines(in cc).


Best regards, Andrey Borodin.


Attachment

pgsql-bugs by date:

Previous
From: Rafia Sabih
Date:
Subject: Re: BUG #19484: Segmentation fault triggered by FDW
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert