From: Josh Berkus <josh@agliodbs.com>
To: Jon Jensen <jon@endpoint.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
Date: Thu, 21 Aug 2003 09:16:29 -0700
Message-ID: <200308210916.29790.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0308211358330.7041-100000@louche.swelter.net>
References: <200308201102.37559.josh@agliodbs.com>
<3F44C6DC.4060105@dunslane.net>
<Pine.LNX.4.50.0308211358330.7041-100000@louche.swelter.net>
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
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: josh@agliodbs.com, jon@endpoint.com, pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
In-Reply-To: <200308210916.29790.josh@agliodbs.com>
* 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