X-Original-To: pgsql-general-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 6E35B9FB2DB
	for <pgsql-general-postgresql.org@postgresql.org>;
	Wed, 16 Aug 2006 09:40:31 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 37782-01 for
	<pgsql-general-postgresql.org@postgresql.org>;
	Wed, 16 Aug 2006 09:40:20 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from mx00.pub.collaborativefusion.com
	(mx00.pub.collaborativefusion.com [206.210.89.199])
	by postgresql.org (Postfix) with ESMTP id A05F79FA612
	for <pgsql-general@postgresql.org>;
	Wed, 16 Aug 2006 09:40:20 -0300 (ADT)
Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com
	[206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by wingspan with esmtp; Wed, 16 Aug 2006 08:40:19 -0400
	id 0005641E.44E31233.0000B66E
Received: from Internal Mail-Server (206.210.89.202) by mx01 (envelope-from
	wmoran@collaborativefusion.com)
	with AES256-SHA encrypted SMTP; 16 Aug 2006 08:34:40 -0400
Date: Wed, 16 Aug 2006 08:40:17 -0400
From: Bill Moran <wmoran@collaborativefusion.com>
To: "Poul =?ISO-8859-1?Q?M=F8ller?= Hansen" <freebsd@pbnet.dk>
Cc: pgsql-general@postgresql.org
Subject: Re: Segmentation Fault
Message-Id: <20060816084017.ee596768.wmoran@collaborativefusion.com>
In-Reply-To: <44E308B2.8030008@pbnet.dk>
References: <44E308B2.8030008@pbnet.dk>
Organization: Collaborative Fusion
X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.07 tagged_above=0 required=5 tests=AWL,
	UNPARSEABLE_RELAY
X-Spam-Level: 
X-Archive-Number: 200608/707
X-Sequence-Number: 99478

In response to "Poul M=F8ller Hansen" <freebsd@pbnet.dk>:

> Last night one of my databases broke down temporary because of a=20
> segmentation fault.
> It has only happended this time and the database was fully recovered=20
> afterwards,
> but I was wondering what I can do anything to prevent it from happening=20
> again
>=20
> It happened while the backup was running (pg_dump & pgdumpall)
> Here are some details from the logs etc.
>=20
> The system is running Ubuntu Linux and I'm using the PostgreSQL package=20
> from the dapper repository:
> uname -a
> Linux db 2.6.15-26-amd64-server #1 SMP Fri Jul 7 20:02:26 UTC 2006=20
> x86_64 GNU/Linux
>=20
> select version()
> PostgreSQL 8.1.4 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.0.gcc-opt=
=20
> (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
>=20
> pgsql log
> 2006-08-16 00:38:22 CEST - LOG:  server process (PID 4792) was=20
> terminated by sig
> nal 11

Sig 11 are frequently the result of hardware problems.  Make sure the
system has enough cooling and consistent power.  Stress test the RAM, MMU,
and other components to ensure that they will function reliably under
load.

--=20
Bill Moran
Collaborative Fusion Inc.