From: Florian Weimer <fw@deneb.enyo.de>
To: Jim C. Nasby <jim@nasby.net>
Cc: Richard Troy <rtroy@ScienceTools.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Craig A. James <cjames@modgraph-usa.com>
Cc: Richard Huxton <dev@archonet.com>
Cc: Russell Smith <mr-russ@pws.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres server crash
Date: Mon, 27 Nov 2006 19:11:57 +0100
Message-ID: <87irh03gk2.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20061126234101.GG39519@nasby.net>
References: <19583.1163700841@sss.pgh.pa.us>
<Pine.LNX.4.33.0611181713170.19262-100000@denzel.in>
<20061126234101.GG39519@nasby.net>
* Jim C. Nasby:
> What's interesting is that apparently FreeBSD also has overcommit (and
> IIRC no way to disable it), yet I never hear people going off on OOM
> kills in FreeBSD. My theory is that FreeBSD admins are smart enough to
> dedicate a decent amount of swap space, so that by the time you got to
> an OOM kill situation you'd be so far into swapping that the box would
> be nearly unusable.
I've seen OOM situations with our regular "use twice as much swap
space as there is RAM in the machine" rule. Perhaps Linux is just
paging too fast for this to work. 8-P
By the way, the sysctl setting breaks some applications and
programming environments, such as SBCL and CMUCL.
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-performance@postgresql.org
Cc: fw@deneb.enyo.de, jim@nasby.net, rtroy@ScienceTools.com, tgl@sss.pgh.pa.us, cjames@modgraph-usa.com, dev@archonet.com, mr-russ@pws.com.au
Subject: Re: Postgres server crash
In-Reply-To: <87irh03gk2.fsf@mid.deneb.enyo.de>
* 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