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 782279DC84B for ; Wed, 21 Dec 2005 14:27:44 -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 90963-08 for ; Wed, 21 Dec 2005 14:27:43 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.dsvr.co.uk (mail.dsvr.co.uk [212.69.192.8]) by postgresql.org (Postfix) with ESMTP id B47BF9DC84A for ; Wed, 21 Dec 2005 14:27:41 -0400 (AST) Received: from [62.69.64.93] (helo=[10.100.3.130]) by mail.dsvr.co.uk with esmtp (Exim 4.30) id 1Ep8gf-00080W-5g; Wed, 21 Dec 2005 18:27:41 +0000 Subject: Re: PostgreSQL 7.4.10 hanging on delete From: Jonathan Parkin To: Tom Lane Cc: PostgreSQL Admin Mailing List In-Reply-To: <13239.1135178345@sss.pgh.pa.us> References: <1135095712.14411.1260.camel@jparkin.local> <300.1135096634@sss.pgh.pa.us> <1135160136.27915.77.camel@jparkin.local> <13239.1135178345@sss.pgh.pa.us> Content-Type: text/plain Organization: Legend Communications plc Message-Id: <1135189491.27921.104.camel@jparkin.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 21 Dec 2005 18:24:51 +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/249 X-Sequence-Number: 19969 > Given the stack traces, I no longer think it's a data corruption issue > --- somehow libc is screwing up. Backends are single-threaded and there > is *no* reason for pthread_mutex_lock to block, ever. > > I have a vague recollection that we saw something similar reported once > before, but it was awhile ago [ digs... ] Here it is: > http://archives.postgresql.org/pgsql-admin/2003-07/msg00303.php > and later > http://archives.postgresql.org/pgsql-admin/2003-08/msg00064.php > > We never did figure out what was up, but it is striking that the other > reporter was also using plpython. It begins to look like Python is > somehow contributing to the problem. What versions of python and > glibc are you running, exactly? glibc-2.3.2 python-2.2.2 postgresql-python-7.4.10 Linux 2.4.20 > If you just want to get your production machine back to stability, > I'd recommend the workaround suggested in that thread, which is to > not use syslog-based logging. Which indeed appears to have stopped this from being a problem. Thank you very much for all the help. If you'd like any more information (e.g. on versions of things) I may not be around until the new year, but I'll happily provide them once I'm back. Thanks again, Jon -- 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.