From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kurt Roeckx <Q@ping.be>
Cc: 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:14:51 -0400
Message-ID: <14777.1061486091@sss.pgh.pa.us> (raw)
In-Reply-To: <20030821171139.GA11389@ping.be>
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>
<14228.1061485453@sss.pgh.pa.us>
<20030821171139.GA11389@ping.be>
Kurt Roeckx <Q@ping.be> writes:
> On Thu, Aug 21, 2003 at 01:04:13PM -0400, Tom Lane wrote:
>> "Fatally corrupted"? That should not happen --- at worst, an OOM kill
>> should lose your current sessions. We need more details.
> Even if it kills the postmaster?
Then you'd have to start a new postmaster. But it still shouldn't
corrupt anything.
(Since the postmaster has small and essentially constant memory usage,
it's a pretty improbable target for the OOM killer, anyway.)
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, Q@ping.be, josh@agliodbs.com, jon@endpoint.com, pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
In-Reply-To: <14777.1061486091@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