From: Daniel Verite <daniel@manitou-mail.org>
To: Kyle Kingsbury <aphyr@jepsen.io>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Potential G2-item cycles under serializable isolation
Date: Wed, 03 Jun 2020 13:51:19 +0200
Message-ID: <6e4c7e1d-e901-4e84-bf37-66b58d0cf8d3@manitou-mail.org> (raw)
In-Reply-To: <3150072e-13b8-7655-211b-17898f894e45@jepsen.io>
Kyle Kingsbury wrote:
> SQL 92 says that the difference between repeatable read and serializable is
> *exactly* the prohibition of P3 ("phantom").
You're probably refering to Table-9 in SQL-92, showing
that P3 can happen under Repeatable Read and cannot happen
under Serializable.
But it doesn't say that the *only* difference between RR and Serializable
is avoiding P3. When defining P1, P2, P3, it doesn't explicitly say
that these are the only anomalies that can arise from concurrency.
The PG doc refers to the other cases as "serialization anomalies".
Compared to the manual, https://wiki.postgresql.org/wiki/Serializable
has more in-depth explanations on the specifics of PG serializable
implementation.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: daniel@manitou-mail.org, aphyr@jepsen.io, pgsql-bugs@lists.postgresql.org
Subject: Re: Potential G2-item cycles under serializable isolation
In-Reply-To: <6e4c7e1d-e901-4e84-bf37-66b58d0cf8d3@manitou-mail.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox