From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Jon Jensen <jon@endpoint.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
Date: Thu, 21 Aug 2003 13:04:13 -0400
Message-ID: <14228.1061485453@sss.pgh.pa.us> (raw)
In-Reply-To: <200308210916.29790.josh@agliodbs.com>
References: <200308201102.37559.josh@agliodbs.com>
<3F44C6DC.4060105@dunslane.net>
<Pine.LNX.4.50.0308211358330.7041-100000@louche.swelter.net>
<200308210916.29790.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, jon@endpoint.com, pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
In-Reply-To: <14228.1061485453@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox