Re: ERRCODE_T_R_DEADLOCK_DETECTED - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ERRCODE_T_R_DEADLOCK_DETECTED
Date
Msg-id 8491.1426819660@sss.pgh.pa.us
Whole thread Raw
In response to Re: ERRCODE_T_R_DEADLOCK_DETECTED  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: ERRCODE_T_R_DEADLOCK_DETECTED
List pgsql-hackers
Tatsuo Ishii <ishii@postgresql.org> writes:
>> 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.

We already have file and line number recorded.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Superuser connect during smart shutdown
Next
From: Tom Lane
Date:
Subject: Re: configure can't detect proper pthread flags