Re: ERRCODE_T_R_DEADLOCK_DETECTED

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: andres(at)2ndquadrant(dot)com, kgrittn(at)ymail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERRCODE_T_R_DEADLOCK_DETECTED
Date: 2015-03-20 02:47:40
Message-ID: 8491.1426819660@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <ishii(at)postgresql(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-20 03:08:38 Re: configure can't detect proper pthread flags
Previous Message Bruce Momjian 2015-03-20 02:42:36 Re: Superuser connect during smart shutdown