X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 83C0E9DCBCF for ; Wed, 21 Dec 2005 06:13:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 94310-02 for ; Wed, 21 Dec 2005 06:13:04 -0400 (AST) X-Greylist: delayed 17:48:14.185838 by SQLgrey- Received: from mail.dsvr.co.uk (mail.dsvr.co.uk [212.69.192.8]) by postgresql.org (Postfix) with ESMTP id 4EFBE9DCBB0 for ; Wed, 21 Dec 2005 06:13:00 -0400 (AST) Received: from [62.69.64.93] (helo=[10.100.3.130]) by mail.dsvr.co.uk with esmtp (Exim 4.30) id 1Ep0xy-0003Jo-DY; Wed, 21 Dec 2005 10:13:02 +0000 Subject: Re: PostgreSQL 7.4.10 hanging on delete From: Jonathan Parkin To: Pandurangan R S Cc: PostgreSQL Admin Mailing List In-Reply-To: <5e744e3d0512210002o7bb0f782oaacdb9a64160e0fe@mail.gmail.com> References: <1135095712.14411.1260.camel@jparkin.local> <5e744e3d0512210002o7bb0f782oaacdb9a64160e0fe@mail.gmail.com> Content-Type: text/plain Organization: Legend Communications plc Message-Id: <1135159805.27920.70.camel@jparkin.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 21 Dec 2005 10:10:05 +0000 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200512/238 X-Sequence-Number: 19958 There are no conflicting locks; this occurs both concurrently with other processes (dealing with other rows) and when the only two processes with locks on the database are the one that hangs and the one I'm using to examine pg_locks. On Wed, 2005-12-21 at 08:02, Pandurangan R S wrote: > When the delete statements hangs, look into the pg_locks table, to > check if the delete statement is waiting because it has conflict with > rows locked by other transactions. > > On 20 Dec 2005 16:21:53 +0000, Jonathan Parkin > wrote: > > I have a reasonably large, live, system-critical database. A perl > > script on another machine connects and issues a sequence of commands in > > a transaction, the last of which is a delete. The delete never returns > > a response, and the connection never times out. The postgres process > > handling the delete is in a scheduled state, but stracing it produces no > > output at all. [Remainder of original message cut for brevity] -- Best Regards Jonathan Parkin Developer Legend Communications plc T: 0844 390 2049 F: 0844 390 2001 E: jonathan.parkin@legendplc.com W: http://www.legend.co.uk/ The information in this message is confidential and may be legally privileged. Unauthorised disclosure, copying or distribution, either whole or in part; or action taken in reliance on its content is prohibited. If you are not the intended recipient, please notify Legend Communications immediately.