Re: deadlock in single-row select-for-update + update scenario? How could it happen?

Поиск
Список
Период
Сортировка
От hubert depesz lubaczewski
Тема Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Дата
Msg-id CAKrjmhcOjXMUHNB5_41_pAtcQ7_QZy+EXoBDdtDj1VU86Cafiw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-general
Дерево обсуждения
On Fri, Aug 22, 2014 at 6:55 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
What transaction isolation level is being used?

Sorry for late reply - the user was away for parts of friday, I was away on weekend, and just now got answer - it's read committed.

depesz

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

Предыдущее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Way to identify the current session's temp tables within pg_class ?