Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id BC4C42E0040 for ; Tue, 13 May 2008 20:00:32 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 18678-07 for ; Tue, 13 May 2008 20:00:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id A1DB42E003A for ; Tue, 13 May 2008 20:00:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m4DN0SQC007587; Tue, 13 May 2008 19:00:28 -0400 (EDT) To: Tino Schwarze cc: pgsql-admin@postgresql.org Subject: Re: Deadlocks ? In-reply-to: <20080513193048.GA15701@easy2.in-chemnitz.de> References: <8490DCB9-7D9B-47E5-B5A6-A0FD52C30C59@kevinkempterllc.com> <20080513193048.GA15701@easy2.in-chemnitz.de> Comments: In-reply-to Tino Schwarze message dated "Tue, 13 May 2008 21:30:48 +0200" Date: Tue, 13 May 2008 19:00:28 -0400 Message-ID: <7586.1210719628@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/113 X-Sequence-Number: 29197 Tino Schwarze 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