Re: Possible G2-item at SERIALIZABLE

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Kyle Kingsbury <aphyr(at)jepsen(dot)io>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Possible G2-item at SERIALIZABLE
Date: 2026-06-01 06:18:58
Message-ID: 802C6ECE-8D49-4E1A-83CB-A45C8E4EBFAD@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 1 Jun 2026, at 06:49, Kyle Kingsbury <aphyr(at)jepsen(dot)io> wrote:
>
> This behavior disappears

Glad that was it. There's a separate case I'd still like your eyes on: savepoints.

README-SSI says predicate locks must survive a subtransaction rollback, because the
subxact's reads still affect what the top transaction writes. By that same reasoning,
shouldn't a serialization failure raised while checking such a read DooM the top
transaction, rather than being swallowed by ROLLBACK TO SAVEPOINT?

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2026-06-01 10:11:46 Re: Possible G2-item at SERIALIZABLE
Previous Message Michael Paquier 2026-06-01 06:18:21 Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert