Documentation Inaccuracy – Transaction Isolation

Поиск
Список
Период
Сортировка
От Nicholson, Brad (Toronto, ON, CA)
Тема Documentation Inaccuracy – Transaction Isolation
Дата
Msg-id EC55DC235432104F8255702A8D7344D951F6CCAD@G4W3211.americas.hpqcorp.net
обсуждение исходный текст
Ответы Re: Documentation Inaccuracy – Transaction Isolation  (Bruce Momjian <bruce@momjian.us>)
Список 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 по дате отправления:

Предыдущее
От: Evan Martin
Дата:
Сообщение: Re: Workaround for bug #13148 (deferred EXCLUDE constraint violation)
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Documentation Inaccuracy – Transaction Isolation