pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonathan Parkin <jonathan.parkin@legendplc.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Admin Mailing List <pgsql-admin@postgresql.org>
Subject: Re: PostgreSQL 7.4.10 hanging on delete
Date: 21 Dec 2005 18:24:51 +0000
Message-ID: <1135189491.27921.104.camel@jparkin.local> (raw)
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>

> 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.




view thread (8+ messages)

Message-ID: <1135189491.27921.104.camel@jparkin.local>
Permalink:  ../1135189491.27921.104.camel@jparkin.local/
Also on:    postgresql.org/message-id/1135189491.27921.104.camel@jparkin.local

 · 

reply

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: jonathan.parkin@legendplc.com, tgl@sss.pgh.pa.us
  Subject: Re: PostgreSQL 7.4.10 hanging on delete
  In-Reply-To: <1135189491.27921.104.camel@jparkin.local>
  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> <1135189491.27921.104.camel@jparkin.local>

* 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