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 CAKrjmhe3+rHUgjAUjQvLiOz55SQ6Fs2qE1PVBOwGaVX3PoYvgw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Список pgsql-general
Дерево обсуждения
On Fri, Aug 22, 2014 at 9:21 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
FWIW this problem was reported also by Andrew Sackville-West at
http://www.postgresql.org/message-id/20140731233051.GN17765@andrew-ThinkPad-X230
I strongly suspect now that the problem is related to the locking of
updated versions as heap_lock_tuple_updated, and perhaps the internal
locking done by EvalPlanQual.  Haven't traced through it.

Is there anything I could tell the developer to do (he's on Mac) so he could provide more information?

depesz

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

Предыдущее
От: hubert depesz lubaczewski
Дата:
Сообщение: 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?