Re: BUG #16454: Mixed isolation levels inside transactions - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #16454: Mixed isolation levels inside transactions
Date
Msg-id CA+hUKGLqCxZsQaybJ9cLWRQBkTEGOJHuzqUhnqBkGxpMS0SeuQ@mail.gmail.com
Whole thread Raw
In response to BUG #16454: Mixed isolation levels inside transactions  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Thu, May 21, 2020 at 12:59 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
> I am seeing mixed/hybrid Isolation Levels when setting the isolation level
> to SERIALIZABLE READ ONLY DEFERRABLE, this also happens with REPEATABLE READ
> READ ONLY. The user tables sees only the data committed before the
> transaction begins but the system tables sees data committed by other
> transactions after the transaction begins. This means in my example the user
> tables are Serializable Isolation Level and the system tables are Read
> Committed Isolation Level.

That is expected behaviour.  Perhaps we're missing a note about it in
the manual?



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Unique constraint error instead of serialization_failure
Next
From: Tom Lane
Date:
Subject: Re: BUG #16454: Mixed isolation levels inside transactions