From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: pgsql-performance@postgresql.org
Subject: Re: Postgres server crash
Date: Sun, 19 Nov 2006 09:07:27 -0800
Message-ID: <ejq30d$2a5p$1@news.hub.org> (raw)
In-Reply-To: <6028.1163919065@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0611181713170.19262-100000@denzel.in>
<455FFD02.1060503@modgraph-usa.com>
<6028.1163919065@sss.pgh.pa.us>
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: rm_pg@cheapcomplexdevices.com
Subject: Re: Postgres server crash
In-Reply-To: <ejq30d$2a5p$1@news.hub.org>
* 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