public inbox for [email protected]
help / color / mirror / Atom feeddoc patch for Linux memory overcommit
3+ messages / 2 participants
[nested] [flat]
* doc patch for Linux memory overcommit
@ 2007-03-06 08:28 Toru SHIMOGAKI <[email protected]>
2007-03-06 08:44 ` Re: doc patch for Linux memory overcommit Peter Eisentraut <[email protected]>
2007-03-06 09:58 ` Re: doc patch for Linux memory overcommit Peter Eisentraut <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: Toru SHIMOGAKI @ 2007-03-06 08:28 UTC (permalink / raw)
To: [email protected]; +Cc: 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<[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>
Attachments:
[text/plain] overcommit_doc.patch (1.2K, 2-overcommit_doc.patch)
download | inline diff:
*** 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>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: doc patch for Linux memory overcommit
2007-03-06 08:28 doc patch for Linux memory overcommit Toru SHIMOGAKI <[email protected]>
@ 2007-03-06 08:44 ` Peter Eisentraut <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Peter Eisentraut @ 2007-03-06 08:44 UTC (permalink / raw)
To: pgsql-docs; +Cc: Toru SHIMOGAKI <[email protected]>; [email protected]
Toru SHIMOGAKI wrote:
> 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.
The text needs some articles.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: doc patch for Linux memory overcommit
2007-03-06 08:28 doc patch for Linux memory overcommit Toru SHIMOGAKI <[email protected]>
@ 2007-03-06 09:58 ` Peter Eisentraut <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Peter Eisentraut @ 2007-03-06 09:58 UTC (permalink / raw)
To: pgsql-docs; +Cc: Toru SHIMOGAKI <[email protected]>; [email protected]
Toru SHIMOGAKI wrote:
> 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.
Patch installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2007-03-06 09:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-03-06 08:28 doc patch for Linux memory overcommit Toru SHIMOGAKI <[email protected]>
2007-03-06 08:44 ` Peter Eisentraut <[email protected]>
2007-03-06 09:58 ` Peter Eisentraut <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox