mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove paragraph about Linux OOM killer and fork(). Instead link to

Browse Source 
article about OOM.
This commit is contained in:
Bruce Momjian 2007-12-22 05:13:03 +00:00
parent cda598e184
commit 25e9b0e36f
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/runtime.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.392 2007/12/17 14:00:52 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.393 2007/12/22 05:13:03 momjian Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
@ -1256,14 +1256,11 @@ Out of Memory: Killed process 12345 (postgres).
<para>
On Linux 2.6 and later, an additional measure is to modify the
kernel's behavior so that it will not <quote>overcommit</> memory.
Although this setting will not prevent the OOM killer from
being invoked altogether, it will lower the chances significantly and
will therefore lead to more robust system behavior. (It might also
cause <function>fork()</> to fail when the machine appears to have
available memory but it is actually reserved
to other applications with careless memory allocation.) This
is done by selecting strict overcommit mode via
<command>sysctl</command>:
Although this setting will not prevent the <ulink
url="http://lwn.net/Articles/104179/">OOM killer</> from being invoked
altogether, it will lower the chances significantly and will therefore
lead to more robust system behavior. This is done by selecting strict
overcommit mode via <command>sysctl</command>:
<programlisting>
sysctl -w vm.overcommit_memory=2
</programlisting>