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

Re: Postgres server crash

From: "Mattias Kregert" <mattias(at)kregert(dot)se>
To: "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Postgres server crash
Date: 2006-11-20 22:36:06
Message-ID: 004f01c70cf4$4565ee10$6e00a8c0@SLUGGO (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
if [ `cat /proc/sys/vm/overcommit_memory` == 0 ]; then
    echo "WARNING: Watch out for the oom-killer! Consider echo 2 > 

----- Original Message ----- 
From: "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>
To: <pgsql-performance(at)postgresql(dot)org>
Sent: Sunday, November 19, 2006 6:07 PM
Subject: Re: Postgres server crash

> Tom Lane wrote:
>> "Craig A. James" <cjames(at)modgraph-usa(dot)com> writes:
>>> Here's something I found googling for "memory overcommitment"+linux
>> That might have been right when it was written (note the reference to a
>> 2.2 Linux kernel), but it's 100% wrong now.  0 is the default, not-safe
>> setting.
> Is this something we could detect and show a warning for at initdb
> time; or perhaps log a warning in the log files at postmaster startup?
> This dangerous choice of settings seems to catch quite a few postgresql
> users.

In response to

pgsql-performance by date

Next:From: Jérôme BENOISDate: 2006-11-21 09:21:29
Subject: BitMapScan performance degradation
Previous:From: Craig A. JamesDate: 2006-11-20 06:42:07
Subject: Re: Postgres server crash

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