Re: algo for canceling a deadlocked transaction

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: algo for canceling a deadlocked transaction
Дата
Msg-id 20180409135121.GJ27724@tamriel.snowman.net
обсуждение исходный текст
Ответ на algo for canceling a deadlocked transaction  (Thomas Poty <thomas.poty@gmail.com>)
Ответы Re: algo for canceling a deadlocked transaction  (Thomas Poty <thomas.poty@gmail.com>)
Список pgsql-general
Greetings,

* Thomas Poty (thomas.poty@gmail.com) wrote:
> My question is : In case of a deadlock between 2 transaction,  how to know
> which transaction will be canceled? Is it predictable?

The short answer is "it's whichever one detected the deadlock."  The
deadlock timeout fires after a lock has been held that long and if a
deadlock is detected then the process detecting it will be canceled.

I'd strongly recommend reviewing your application and addressing
deadlocks by changing how the application acquires locks to be
consistent and to avoid lock escalation instead of worrying about how to
predict a deadlock- a properly designed and written application
shouldn't be causing deadlocks to happen in the first place.

Thanks!

Stephen

Вложения

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

Предыдущее
От: Thomas Poty
Дата:
Сообщение: algo for canceling a deadlocked transaction
Следующее
От: Melvin Davidson
Дата:
Сообщение: Re: Rationale for aversion to the central database?