Re: Improving deadlock error messages - Mailing list pgsql-hackers

From Neil Conway
Subject Re: Improving deadlock error messages
Date
Msg-id 1177091158.16415.90.camel@localhost.localdomain
Whole thread Raw
In response to Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2007-04-20 at 02:55 -0400, Tom Lane wrote:
> I don't think you've thought of quite all of the failure cases.  One
> that's a bit pressing is that a deadlock isn't necessarily confined to
> objects in your own database.

I'm not sure I follow. If we conditionally acquire the locks we need and
always fallback to just printing the numeric OIDs, ISTM we should be
able to avoid the infinite recursion problem. (If necessary, we can
always special-case objects outside our own database, although I'm not
sure that's necessary.)

-Neil




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
Next
From: Gregory Stark
Date:
Subject: 27 second plan times