Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8BBA89FB27E for ; Tue, 6 Mar 2007 03:00:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 01372-10 for ; Tue, 6 Mar 2007 02:59:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from serv1.oss.ntt.co.jp (ns.oss.ntt.co.jp [222.151.198.98]) by postgresql.org (Postfix) with ESMTP id 0F6E89FB225 for ; Tue, 6 Mar 2007 02:59:52 -0400 (AST) Received: from [127.0.0.1] (unknown [172.17.1.114]) by serv1.oss.ntt.co.jp (Postfix) with ESMTP id C9B33104004; Tue, 6 Mar 2007 15:59:49 +0900 (JST) Message-ID: <45ED1123.8040508@oss.ntt.co.jp> Date: Tue, 06 Mar 2007 15:58:43 +0900 From: Toru SHIMOGAKI User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jim Nasby CC: pgsql-docs@postgresql.org Subject: Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer References: <45E811CB.8040300@oss.ntt.co.jp> <741C8ABF-0ABD-4907-992D-F09C232411FC@decibel.org> In-Reply-To: <741C8ABF-0ABD-4907-992D-F09C232411FC@decibel.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.051 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200703/3 X-Sequence-Number: 4174 Jim Nasby wrote: > On Mar 2, 2007, at 6:00 AM, Toru SHIMOGAKI wrote: >> I think that to avoid this problem, "increasing swap area" should be >> added on >> this manual. Increasing both physical memory and swap area is easy to >> understand, but increasing physical memory is not software solution. > > Good idea; care to submit a patch? :) Yes, I'll submit a patch as soon as possible. -- Toru SHIMOGAKI