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

From Gregory Stark
Subject Re: Improving deadlock error messages
Date
Msg-id 87irbra0fk.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Improving deadlock error messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> 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.

We could do the syscache lookups for only the object we're waiting on and
store that information in the lock table for others to refer to. We would have
to do the syscache lookup either always or at the point where we first decide
we have to block.


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Marcin Waldowski
Date:
Subject: Re: [BUGS] BUG #3242: FATAL: could not unlock semaphore: error code 298
Next
From: Koichi Suzuki
Date:
Subject: Re: [PATCHES] Full page writes improvement, code update