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 CAKrjmhcW97_Mivy-5-JuUXExgJ3ZOXLJeE3G5B5x_Xpe8tK+Lw@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?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Список pgsql-general
Дерево обсуждения
On Fri, Aug 22, 2014 at 7:54 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
Which in itself might be a clue.

Is all the code/data running on/coming from that machine or is some coming in remotely?

Where network latency might be an issue?

All locally, but hey - how could network latency be a problem? Transaction gets the lock on row, and then it updates. the same row. in the same transaction. with nothing else in the transaction. where is here place for deadlock for another, identical transaction?

depesz

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

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