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 BE974D1B8C8 for ; Thu, 21 Aug 2003 14:05:05 -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 80773-03 for ; Thu, 21 Aug 2003 14:04:34 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 55EE4D1B574 for ; Thu, 21 Aug 2003 14:04:33 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h7LH4D5H014229; Thu, 21 Aug 2003 13:04:18 -0400 (EDT) To: Josh Berkus Cc: Jon Jensen , pgsql-hackers@postgresql.org Subject: Re: Can't find thread on Linux memory overcommit In-reply-to: <200308210916.29790.josh@agliodbs.com> References: <200308201102.37559.josh@agliodbs.com> <3F44C6DC.4060105@dunslane.net> <200308210916.29790.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Thu, 21 Aug 2003 09:16:29 -0700" Date: Thu, 21 Aug 2003 13:04:13 -0400 Message-ID: <14228.1061485453@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/953 X-Sequence-Number: 42610 Josh Berkus writes: > Well, sadly, the reason I posted is that I (apparently) had a client's > database fatally corrupted by this problem. "Fatally corrupted"? That should not happen --- at worst, an OOM kill should lose your current sessions. We need more details. regards, tom lane