doc patch for Linux memory overcommit

From: Toru SHIMOGAKI
Subject: doc patch for Linux memory overcommit
Date: ,
Msg-id: 45ED2624.80704@oss.ntt.co.jp
(view: Whole thread, Raw)
Responses: Re: doc patch for Linux memory overcommit  (Peter Eisentraut)
Re: doc patch for Linux memory overcommit  (Peter Eisentraut)
List: pgsql-docs

The attached is a doc patch for Linux memory overcommit and an additional way of
avoiding a problem that postmaster is suddenly killed by OOM-Killer.

http://archives.postgresql.org/pgsql-docs/2007-03/msg00000.php

Best regards,

--
Toru SHIMOGAKI<>
*** runtime.sgml.orig    2007-03-06 16:23:10.000000000 +0900
--- runtime.sgml    2007-03-06 17:14:38.000000000 +0900
***************
*** 1207,1215 ****
     </para>

     <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's
!     behavior so that it will not <quote>overcommit</> memory.  This is
!     done by selecting strict overcommit mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>
--- 1207,1224 ----
     </para>

     <para>
!     In addition, increasing swap area on OS can avoid the problem too.
!     Out-of-Memory-Killer(OOM-Killer) is invoked whenever physical memory and
!     swap area are exhausted. Increasing swap area is easy to set and it
!     doesn't have harmful influence.
!    </para>
!
!    <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's
!     behavior so that it will not <quote>overcommit</> memory.  Though this
!     setting can't prevent OOM-Killer from invoking directly, we can expect
!     healty memory allocation. This is done by selecting strict overcommit
!     mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>


pgsql-docs by date:

From: Peter Eisentraut
Date:
Subject: Re: doc patch for Linux memory overcommit
From: Mark Stosberg
Date:
Subject: suggestion for improving TMPDIR and "--format" docs for pg_dump