Re: ERRCODE_T_R_DEADLOCK_DETECTED

Поиск
Список
Период
Сортировка
От Tatsuo Ishii
Тема Re: ERRCODE_T_R_DEADLOCK_DETECTED
Дата
Msg-id 20150319.233121.1828201312337146789.t-ishii@sraoss.co.jp
обсуждение исходный текст
Ответ на Re: ERRCODE_T_R_DEADLOCK_DETECTED  (Kevin Grittner <kgrittn@ymail.com>)
Ответы Re: ERRCODE_T_R_DEADLOCK_DETECTED
Список pgsql-hackers
> That SQLSTATE value is intended to be used where the transaction
> has failed because it was run concurrently with some other
> transaction, rather than before or after it; and it is intended to
> suggest that the transaction may succeed if run after the competing
> transaction has completed.  If those apply, it seems like the right
> SQLSTATE.  A user can certainly distinguish between the conditions
> by looking at the error messages.

It is sad for users the only way to distinguish the conditions is by
looking at the error messages. They want to know the root of the
problem.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: "cancelling statement due to user request error" occurs but the transaction has committed.
Следующее
От: Andres Freund
Дата:
Сообщение: Re: ERRCODE_T_R_DEADLOCK_DETECTED