From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daniel Bickler <daniel.bickler@goprominent.com>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Serializable Transaction Anomoly
Date: Tue, 05 Nov 2024 20:17:04 +0100
Message-ID: <c8b162966097d43e7d77f39f7a9f206f64a0572f.camel@cybertec.at> (raw)
In-Reply-To: <PH0PR17MB5890CF28F6DD6FA19E76A9D898522@PH0PR17MB5890.namprd17.prod.outlook.com>
References: <173081912264.705.9788227512147158659@wrigleys.postgresql.org>
<12ba622133fe91e9ecfb5a74ae80d74253d1956b.camel@cybertec.at>
<PH0PR17MB5890CF28F6DD6FA19E76A9D898522@PH0PR17MB5890.namprd17.prod.outlook.com>
On Tue, 2024-11-05 at 18:41 +0000, Daniel Bickler wrote:
> The way I interpreted the documentation, the example I ran into was a false negative
> according to the definition of a serialization anomaly, because it’s serial in one
> ordering but not the other which seems incorrect with “all possible”.
>
> I think where I don’t fully understand is the documentation seems to imply all serial
> orderings must be valid to commit a SERIALIZABLE transaction but it seems like just
> one serial ordering must be valid?
You seem to think that transactions are serializable if their result is consistent
with all possible serial execution orders. But that is not so.
What the documentation says is:
It is an serialization anomaly (that is, not serializable) if the execution is
*in*consistent will all possible serial executions.
That implies: It is serializable if the execution is consistent with one serial
execution.
Yours,
Laurenz Albe
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-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, daniel.bickler@goprominent.com, pgsql-docs@lists.postgresql.org
Subject: Re: Serializable Transaction Anomoly
In-Reply-To: <c8b162966097d43e7d77f39f7a9f206f64a0572f.camel@cybertec.at>
* 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