From: Mattias Kregert <mattias@kregert.se>
To: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres server crash
Date: Mon, 20 Nov 2006 23:36:06 +0100
Message-ID: <004f01c70cf4$4565ee10$6e00a8c0@SLUGGO> (raw)
References: <Pine.LNX.4.33.0611181713170.19262-100000@denzel.in>
<455FFD02.1060503@modgraph-usa.com>
<6028.1163919065@sss.pgh.pa.us>
<ejq30d$2a5p$1@news.hub.org>
if [ `cat /proc/sys/vm/overcommit_memory` == 0 ]; then
echo "WARNING: Watch out for the oom-killer! Consider echo 2 >
/proc/sys/vm/overcommit_memory"
fi
----- Original Message -----
From: "Ron Mayer" <rm_pg@cheapcomplexdevices.com>
To: <pgsql-performance@postgresql.org>
Sent: Sunday, November 19, 2006 6:07 PM
Subject: Re: Postgres server crash
> Tom Lane wrote:
>> "Craig A. James" <cjames@modgraph-usa.com> writes:
>>> Here's something I found googling for "memory overcommitment"+linux
>>> http://archives.neohapsis.com/archives/postfix/2000-04/0512.html
>>
>> 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.
>
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: mattias@kregert.se, rm_pg@cheapcomplexdevices.com
Subject: Re: Postgres server crash
In-Reply-To: <004f01c70cf4$4565ee10$6e00a8c0@SLUGGO>
* 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