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 CAKrjmhd34dzZrStCC9A3LZucWTEFNtiYBSuii08kOuY6H9wKAg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Ответы Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Список pgsql-general
Дерево обсуждения
On Fri, Aug 22, 2014 at 7:20 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
So why are different processes running the exact same queries coming in on different ports?

the importer is parallelized, and sometimes two processes handle batches of data that happen to update the same "top level row".

but the deadlocking problem is happening only on one machine, though very repeatably.

depesz

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

Предыдущее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: deadlock in single-row select-for-update + update scenario? How could it happen?