From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jonathan Ellis <jbe(at)familyellis(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: detecting deadlocks |
Date: | 2002-01-23 02:31:57 |
Message-ID: | 200201230231.g0N2Vvj08799@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > * list of locks held by each (so you could guess what had preceeded)
>
> The trouble is that what we've got at that level is a "lock tag" that's
> just some numbers. It's difficult (maybe even impossible in some cases)
> to reverse that into something a user would recognize. Still, we could
> probably do it in enough cases to be useful.
>
> Hey Bruce, do we have a TODO item about giving better deadlock error
> messages?
All we have now is:
o Add SHOW command to display locks
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2002-01-23 03:00:15 | Re: sql scripts |
Previous Message | Nic Ferrier | 2002-01-23 02:27:49 | Re: implemention of calls to stored procs. |