Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jan Behrens <jbe-mlist(at)magnetkern(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only
Date: 2020-11-27 04:24:04
Message-ID: d38b412d9e4866ba008d5e649268570c175b2b04.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2020-11-27 04:25:21 Re: postgres_fdw insert extremely slow
Previous Message Jan Behrens 2020-11-27 01:19:11 Re: Transaction isolation level Repeatable Read Read Only vs Serializable Read Only