Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only
Date
Msg-id d38b412d9e4866ba008d5e649268570c175b2b04.camel@cybertec.at
Whole thread Raw
In response to Transaction isolation level Repeatable Read Read Only vs Serializable Read Only  (Jan Behrens <jbe-mlist@magnetkern.de>)
List pgsql-general
On Thu, 2020-11-26 at 23:45 +0100, Jan Behrens wrote:
> I understand that in a read+write scenario, two concurrent transactions may still lead to
>  a result that could not have occurred if those two transactions were executed one after the other.
>  However, in a read-only case, I do not see how REPEATABLE READ could differ from SERIALIZABLE. Yet [1] explains
that:

There is an example in the Wiki:
https://wiki.postgresql.org/wiki/SSI#Read_Only_Transactions

In that example, serializability is broken only because of a READ ONLY transaction.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: Jan Behrens
Date:
Subject: Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only
Next
From: Laurenz Albe
Date:
Subject: Re: postgres_fdw insert extremely slow