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 285669DC809 for ; Wed, 21 Dec 2005 11:19:07 -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 38566-08 for ; Wed, 21 Dec 2005 11:19:08 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D13489DC807 for ; Wed, 21 Dec 2005 11:19:01 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBLFJ5Ql013240; Wed, 21 Dec 2005 10:19:05 -0500 (EST) To: Jonathan Parkin cc: PostgreSQL Admin Mailing List Subject: Re: PostgreSQL 7.4.10 hanging on delete In-reply-to: <1135160136.27915.77.camel@jparkin.local> References: <1135095712.14411.1260.camel@jparkin.local> <300.1135096634@sss.pgh.pa.us> <1135160136.27915.77.camel@jparkin.local> Comments: In-reply-to Jonathan Parkin message dated "21 Dec 2005 10:15:36 +0000" Date: Wed, 21 Dec 2005 10:19:05 -0500 Message-ID: <13239.1135178345@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.026 required=5 tests=[AWL=0.026] X-Spam-Score: 0.026 X-Spam-Level: X-Archive-Number: 200512/243 X-Sequence-Number: 19963 Jonathan Parkin writes: > On Tue, 2005-12-20 at 16:37, Tom Lane wrote: >> If this is a specific row causing the issue, then I'd wonder about >> data corruption of some sort. It might be worth looking at the >> table with pg_filedump (from http://sources.redhat.com/rhdb/). > Our current plan is to do a rebuild of the database tonight (UK time). > This would hopefully eliminate any such data corruption. 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? 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. regards, tom lane