Re: determine snapshot after obtaining locks for first statement

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: determine snapshot after obtaining locks for first statement
Дата
Msg-id 3541.1261069199@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: determine snapshot after obtaining locks for first statement  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Ответы Re: determine snapshot after obtaining locks for first statement  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Thanks for the clarification.  That does not work for SERIALIZABLE
> at all, because other tables or rows referenced in that first
> statement would be using the original snapshot.  Indeed, the
> behavior under READ COMMITTED could be astonishing in certain
> circumstances as it breaks atomicity:

Yup.  That is stated fairly clearly already in the description of
READ COMMITTED mode, no?
http://developer.postgresql.org/pgdocs/postgres/transaction-iso.html#XACT-READ-COMMITTED
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: determine snapshot after obtaining locks for first statement
Следующее
От: Andrew Dunstan
Дата:
Сообщение: COPY IN as SELECT target