X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [64.117.224.130])
	by svr1.postgresql.org (Postfix) with ESMTP id 853F5D1B550
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu, 21 Aug 2003 16:24:48 -0300 (ADT)
Received: from svr1.postgresql.org ([64.117.224.193])
	by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new,
	port 10024) with ESMTP id 20439-05
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu, 21 Aug 2003 16:24:18 -0300 (ADT)
Received: from davinci.ethosmedia.com (unknown [209.128.84.228])
	by svr1.postgresql.org (Postfix) with ESMTP id 2238DD1BB7A
	for <pgsql-hackers@postgresql.org>;
	Thu, 21 Aug 2003 16:24:16 -0300 (ADT)
Received: from [66.219.92.2] (HELO temoku)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 3534267; Thu, 21 Aug 2003 12:24:08 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Can't find thread on Linux memory overcommit
Date: Thu, 21 Aug 2003 12:22:21 -0700
User-Agent: KMail/1.4.3
Cc: Jon Jensen <jon@endpoint.com>, pgsql-hackers@postgresql.org
References: <200308201102.37559.josh@agliodbs.com>
	<200308210916.29790.josh@agliodbs.com>
	<14228.1061485453@sss.pgh.pa.us>
In-Reply-To: <14228.1061485453@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200308211222.21036.josh@agliodbs.com>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200308/960
X-Sequence-Number: 42617

Folks,

> > Well, sadly, the reason I posted is that I (apparently) had a client's=
=20
> > database fatally corrupted by this problem.=20=20

OK, diagnosis progresses, it's not the Linux OOM problem, it's something el=
se.=20=20

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco