DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=hDfKBRMR4aFqtYS0LLZP+KPgRVGwn1DTA0SXBm3WnLlVtVyc5bKfcNLCVUlE/Y1STIxTm9iCoQDR9krpqi42AjPvV5cTEkKW1wfmhdl086Vwr/WJP1AhIlFjrCrfZ/Uv+j+ZGKoKGUArQfOIKzIEYDZSy2EGTnxSfChokTwrOIw=;
Message-ID: <583856.4119.qm@web39705.mail.mud.yahoo.com>
Date: Mon, 7 Mar 2011 21:25:09 -0800 (PST)
From: Bob Lunney <bob_lunney@yahoo.com>
Subject: Re: PG Server Crash
To: pgsql-admin@postgresql.org
In-Reply-To: <624088.44544.qm@web39706.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Sorry, I should have included the fact that PG was compiled from source on =
the same machine where it runs using gcc 4.1.0, and config.log has:=0A=0A./=
configure --with-python --with-gssapi --enable-thread-safety=0A=0ABob Lunne=
y=0A=0A--- On Mon, 3/7/11, Bob Lunney <bob_lunney@yahoo.com> wrote:=0A=0A> =
From: Bob Lunney <bob_lunney@yahoo.com>=0A> Subject: [ADMIN] PG Server Cras=
h=0A> To: pgsql-admin@postgresql.org=0A> Date: Monday, March 7, 2011, 11:24=
 PM=0A> OK, I got a nasty surprise=0A> today.=A0 The server threw everybody=
 out of the pool and=0A> logged this:=0A> =0A> 10.224.12.4(52763) idle: pth=
read_mutex_lock.c:80:=0A> __pthread_mutex_lock: Assertion `mutex->__data.__=
owner =3D=3D=0A> 0' failed.=0A> :4d45a006.78ec:2011-03-07 11:57:45.316 EST:=
LOG:=A0=0A> server process (PID 21298) was terminated by signal 6:=0A> Abor=
ted=0A> :4d45a006.78ec:2011-03-07 11:57:45.316 EST:LOG:=A0=0A> terminating =
any other active server processes=0A> =0A> It then stopped all the backends=
, restarted, recovered and=0A> worked fine for the rest of the day.=0A> =0A=
> The particulars:=0A> =0A> SLES 10=0A> PG 8.4.1=0A> 8-way Intel Xeon E5345=
 @ 2.33GHz=0A> 32 GB RAM=0A> =0A> max_connections =3D 1500=0A> shared_buffe=
rs =3D 1536MB=0A> work_mem =3D 32MB=A0 =A0 =A0 =A0 =A0 =A0=0A> =A0 =A0 =A0 =
=A0 =A0 =A0=A0=A0=0A> maintenance_work_mem =3D 256MB=A0 =A0 =A0 =A0=0A> =A0=
 =A0 =0A> checkpoint_segments =3D 2048=0A> effective_cache_size =3D 20GB=0A=
> effective_io_concurrency =3D 6=0A> random_page_cost =3D 2.0=0A> =0A> =0A>=
 This server has been rock solid running 8.4.1 for over a=0A> year.=A0 It h=
as Slony replicating to another mirror image=0A> server that has not had an=
y problems whatsoever.=0A> =0A> Any ideas?=0A> =0A> Thanks in advance for a=
ll your help, and especially for the=0A> amazing database software!=0A> =0A=
> Regards,=0A> =0A> Bob Lunney=0A> =0A> =0A> =A0 =A0 =A0 =0A> =0A> -- =0A> =
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)=0A> To make =
changes to your subscription:=0A> http://www.postgresql.org/mailpref/pgsql-=
admin=0A> =0A=0A=0A