Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id D83929F98F8 for ; Sun, 19 Nov 2006 13:07:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.60]) (amavisd-new, port 10024) with ESMTP id 92864-02 for ; Sun, 19 Nov 2006 13:07:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 93AF29F94F3 for ; Sun, 19 Nov 2006 13:07:28 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 6DBC1308EA; Sun, 19 Nov 2006 18:07:27 +0100 (MET) From: Ron Mayer X-Newsgroups: pgsql.performance Subject: Re: Postgres server crash Date: Sun, 19 Nov 2006 09:07:27 -0800 Organization: Hub.Org Networking Services Lines: 13 Message-ID: References: <455FFD02.1060503@modgraph-usa.com> <6028.1163919065@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Icedove 1.5.0.7 (X11/20061013) In-Reply-To: <6028.1163919065@sss.pgh.pa.us> To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/159 X-Sequence-Number: 21929 Tom Lane wrote: > "Craig A. James" 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.