Skip site navigation (1) Skip section navigation (2)

Re: Postgres server crash

From: Florian Weimer <fw(at)deneb(dot)enyo(dot)de>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Richard Troy <rtroy(at)ScienceTools(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres server crash
Date: 2006-11-27 18:11:57
Message-ID: 87irh03gk2.fsf@mid.deneb.enyo.de (view raw or flat)
Thread:
Lists: pgsql-performance
* 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.

In response to

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2006-11-27 18:59:48
Subject: Re: When to vacuum a table?
Previous:From: Guido NeitzerDate: 2006-11-27 16:21:37
Subject: Re: shared_buffers > 284263 on OS X

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group