pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tino Schwarze <postgresql@tisc.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Deadlocks ?
Date: Tue, 13 May 2008 19:00:28 -0400
Message-ID: <7586.1210719628@sss.pgh.pa.us> (raw)
In-Reply-To: <20080513193048.GA15701@easy2.in-chemnitz.de>
References: <8490DCB9-7D9B-47E5-B5A6-A0FD52C30C59@kevinkempterllc.com>
	<20080513193048.GA15701@easy2.in-chemnitz.de>

Tino Schwarze <postgresql@tisc.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



view thread (7+ messages)  latest in thread

Message-ID: <7586.1210719628@sss.pgh.pa.us>
Permalink:  ../7586.1210719628@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/7586.1210719628@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, postgresql@tisc.de
  Subject: Re: Deadlocks ?
  In-Reply-To: <7586.1210719628@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox