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@xxxxxxxxxxxxxxxxxxxxxxx>
To: <pgsql-performance@xxxxxxxxxxxxxx>
Sent: Sunday, November 19, 2006 6:07 PM
Subject: Re: Postgres server crash
Tom Lane wrote:
"Craig A. James" <cjames@xxxxxxxxxxxxxxxx> 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.
