| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | lalbin(at)scharp(dot)org, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16454: Mixed isolation levels inside transactions |
| Date: | 2020-05-21 01:56:47 |
| Message-ID: | CA+hUKGLqCxZsQaybJ9cLWRQBkTEGOJHuzqUhnqBkGxpMS0SeuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, May 21, 2020 at 12:59 PM PG Bug reporting form
<noreply(at)postgresql(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-21 02:14:02 | Re: BUG #16454: Mixed isolation levels inside transactions |
| Previous Message | Thomas Munro | 2020-05-21 01:46:24 | Re: Unique constraint error instead of serialization_failure |