Re: determine snapshot after obtaining locks for first statement

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: determine snapshot after obtaining locks for first statement
Дата
Msg-id 4B2A1B2B020000250002D703@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: determine snapshot after obtaining locks for first statement  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: determine snapshot after obtaining locks for first statement  (Robert Haas <robertmhaas@gmail.com>)
Re: determine snapshot after obtaining locks for first statement  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm not very sure what a clearer explanation would look like
As a stab at it, how about?:
This behavior makes Read Committed mode unsuitable for many UPDATE
or DELETE commands with joins or subqueries
-Kevin

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

Предыдущее
От: Greg Stark
Дата:
Сообщение: Re: determine snapshot after obtaining locks for first statement
Следующее
От: Tom Lane
Дата:
Сообщение: Re: determine snapshot after obtaining locks for first statement