Re: Possible G2-item at SERIALIZABLE

From: Kyle Kingsbury <aphyr(at)jepsen(dot)io>
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-06-01 01:49:47
Message-ID: f8d65719-3570-4ac3-8b67-5dc3da271a55@jepsen.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 5/31/26 08:19, Andrey Borodin wrote:
> Could you confirm whether you still observe G2-item anomalies with a server
> configured default_transaction_isolation = 'serializable' (so that the
> single-statement operations are certainly Serializable)? If they persist under that
> setting I'll dig further...

<sigh>

Yes, this was it, thank you. I've been reworking a whole bunch of things
to make these tests portable between DBs and totally lost the
session-wide transaction isolation. This behavior disappears with:

SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL SERIALIZABLE;

Thank you kindly, Andrey. :-)

--Kyle

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-06-01 02:11:52 Re: BUG #19494: Error on transaction commit inside pipeline triggers psql's Assert
Previous Message Pierre Juhen 2026-05-31 16:47:03 Re: BUG #19502: unix_socket_group doesn't work anymore