Documentation Inaccuracy – Transaction Isolation

From: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Documentation Inaccuracy – Transaction Isolation
Date: 2015-04-28 20:00:24
Message-ID: EC55DC235432104F8255702A8D7344D951F6CCAD@G4W3211.americas.hpqcorp.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I noticed an inaccuracy in the transaction isolation docs. Under the Repeatable Read Isolation Level section it states:

“The Repeatable Read isolation level only sees data committed before the transaction began; it never sees either uncommitted data or changes committed during transaction execution by concurrent transactions.”

That is not entirely accurate. The snapshot starts with the first SQL statement in the transaction, not at the start of the transaction. Any change that is committed in another transaction after the start of the transaction but before the first SQL statement will be seen.

Brad.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2015-04-28 20:23:34 Re: Documentation Inaccuracy – Transaction Isolation
Previous Message Evan Martin 2015-04-28 19:56:41 Re: Workaround for bug #13148 (deferred EXCLUDE constraint violation)