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 5B6BBD1B974 for ; Thu, 21 Aug 2003 13:17:39 -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 65792-01 for ; Thu, 21 Aug 2003 13:17:29 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 57E46D1B9CD for ; Thu, 21 Aug 2003 13:17:28 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3533693; Thu, 21 Aug 2003 09:17:25 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Jon Jensen , pgsql-hackers@postgresql.org Subject: Re: Can't find thread on Linux memory overcommit Date: Thu, 21 Aug 2003 09:16:29 -0700 User-Agent: KMail/1.4.3 References: <200308201102.37559.josh@agliodbs.com> <3F44C6DC.4060105@dunslane.net> In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200308210916.29790.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/951 X-Sequence-Number: 42608 Guys, > So there's no need to wonder whether that's a source of trouble for your > PostgreSQL processes or not; just check the logs. I've had the OOM killer > go after large Perl processes and X, but never (yet) PostgreSQL, I'm happy > to say. Well, sadly, the reason I posted is that I (apparently) had a client's database fatally corrupted by this problem. Downloading Alan Cox's patch now .... -- Josh Berkus Aglio Database Solutions San Francisco