Re: ERRCODE_T_R_DEADLOCK_DETECTED - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: ERRCODE_T_R_DEADLOCK_DETECTED
Date
Msg-id 20150320.113604.152657161127240193.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: ERRCODE_T_R_DEADLOCK_DETECTED  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: ERRCODE_T_R_DEADLOCK_DETECTED  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> 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.
> 
> Sure. It's always a balance. If you go to the extreme of your argument
> every possible error gets one individual error code. But then error
> handling gets too complex.

I think the solution for this is assigning a unique id to each
message.  This is already done in some commercial databases. They are
pretty usefull for tech supports.

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 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: configure can't detect proper pthread flags
Next
From: Bruce Momjian
Date:
Subject: Re: get_actual_variable_range vs idx_scan/idx_tup_fetch