Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id 2072E9FA37A for ; Mon, 20 Nov 2006 18:58:26 -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 13037-03-5 for ; Mon, 20 Nov 2006 18:58:14 -0400 (AST) X-Greylist: delayed 00:21:19.086766 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 292CB9FA618 for ; Mon, 20 Nov 2006 18:58:00 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from www.soravastra.se (1-1-2-32a.osr.sth.bostream.se [82.182.182.84]) by svr4.postgresql.org (Postfix) with ESMTP id 9C9FB5AF8DA for ; Mon, 20 Nov 2006 22:36:39 +0000 (GMT) Received: from SLUGGO ([192.168.0.110]) by www.soravastra.se (8.12.11/8.12.11) with SMTP id kAKMqLRh023944; Mon, 20 Nov 2006 23:52:21 +0100 Message-ID: <004f01c70cf4$4565ee10$6e00a8c0@SLUGGO> From: "Mattias Kregert" To: "Ron Mayer" Cc: References: <455FFD02.1060503@modgraph-usa.com> <6028.1163919065@sss.pgh.pa.us> Subject: Re: Postgres server crash Date: Mon, 20 Nov 2006 23:36:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/169 X-Sequence-Number: 21939 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" To: Sent: Sunday, November 19, 2006 6:07 PM Subject: Re: Postgres server crash > 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. >