| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tino Schwarze <postgresql(at)tisc(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Deadlocks ? |
| Date: | 2008-05-13 23:00:28 |
| Message-ID: | 7586.1210719628@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tino Schwarze <postgresql(at)tisc(dot)de> writes:
> On Tue, May 13, 2008 at 01:18:24PM -0600, kevin kempter wrote:
> ProgrammingError: deadlock detected
> DETAIL: Process 23098 waits for ShareUpdateExclusiveLock on
> relation 428126 of database 427376; blocked by process 23916.
> Process 23916 waits for ShareLock on transaction 46802680; blocked
> by process 23098.
> I've never figured out how to resolve the "lock on transaction" to
> something understandable...
It's presumably waiting for a row lock that the other transaction
has got. We don't keep enough information about row locks in memory
to give a better error message (because we could run out of memory
if we tried :-()
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kevin kempter | 2008-05-13 23:33:27 | Re: Deadlocks ? |
| Previous Message | Tino Schwarze | 2008-05-13 19:30:48 | Re: Deadlocks ? |