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<[EMAIL PROTECTED]>
*** 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>
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
