From: Josh Berkus <josh@agliodbs.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
Date: Thu, 21 Aug 2003 10:13:26 -0700
Message-ID: <200308211013.26737.josh@agliodbs.com> (raw)
In-Reply-To: <3F44F6A1.8090900@dunslane.net>
References: <200308201102.37559.josh@agliodbs.com>
<200308210919.48463.josh@agliodbs.com>
<3F44F6A1.8090900@dunslane.net>
Alan,
> You need to be careful using Alan's patch. The reason RH stopped using
> this part of it in their errata kernels is that it had conflicts with
> other stuff, specifically the rmap stuff (he told me that himself in
> email).
Hmmm ... that leaves us without a workaround for this problem, then, yes?
Because even parnoid-mode kernels you can discourage, but not prevent,
overcommitting.
> For mission critical apps I would advise running the postmaster on a
> dedicated machine, with no X or other nasty stuff running.
Unfortunately, this is frequently not an option ... PostgreSQL is often
together on a server with Apache, a JVM, and other server software. As
happened in the one case of possible (diagnosis pending) failure that we are
looking into. Of course, it could be something else ....
--
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, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: Can't find thread on Linux memory overcommit
In-Reply-To: <200308211013.26737.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