Documentation Inaccuracy – Transaction Isolation - Mailing list pgsql-general

From Nicholson, Brad (Toronto, ON, CA)
Subject Documentation Inaccuracy – Transaction Isolation
Date
Msg-id EC55DC235432104F8255702A8D7344D951F6CCAD@G4W3211.americas.hpqcorp.net
Whole thread Raw
Responses Re: Documentation Inaccuracy – Transaction Isolation
List 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
uncommitteddata 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
ofthe transaction.  Any change that is committed in another transaction after the start of the transaction but before
thefirst SQL statement will be seen. 

Brad.




pgsql-general by date:

Previous
From: Evan Martin
Date:
Subject: Re: Workaround for bug #13148 (deferred EXCLUDE constraint violation)
Next
From: Bruce Momjian
Date:
Subject: Re: Documentation Inaccuracy – Transaction Isolation