| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | kgrittn(at)ymail(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ERRCODE_T_R_DEADLOCK_DETECTED |
| Date: | 2015-03-19 14:31:21 |
| Message-ID: | 20150319.233121.1828201312337146789.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-03-19 14:33:54 | Re: ERRCODE_T_R_DEADLOCK_DETECTED |
| Previous Message | Bruce Momjian | 2015-03-19 14:23:54 | Re: "cancelling statement due to user request error" occurs but the transaction has committed. |