Re: ERRCODE_T_R_DEADLOCK_DETECTED

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: andres(at)2ndquadrant(dot)com
Cc: kgrittn(at)ymail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERRCODE_T_R_DEADLOCK_DETECTED
Date: 2015-03-20 02:36:04
Message-ID: 20150320.113604.152657161127240193.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-03-20 02:38:52 Re: get_actual_variable_range vs idx_scan/idx_tup_fetch
Previous Message Bruce Momjian 2015-03-20 02:22:31 Re: configure can't detect proper pthread flags