From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonathan Parkin <jonathan.parkin@legendplc.com>
Cc: PostgreSQL Admin Mailing List <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL 7.4.10 hanging on delete
Date: Wed, 21 Dec 2005 10:19:05 -0500
Message-ID: <13239.1135178345@sss.pgh.pa.us> (raw)
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>
Jonathan Parkin <jonathan.parkin@legendplc.com> 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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jonathan.parkin@legendplc.com
Subject: Re: PostgreSQL 7.4.10 hanging on delete
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>
* 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