Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit e5a9ef5

Browse files
committed
Add docs about OOM killer.
lst_hoe01@kwsoft.de
1 parent 3e4c6b5 commit e5a9ef5

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

doc/src/sgml/runtime.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.387 2007/12/16 10:17:13 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.388 2007/12/16 11:22:33 momjian Exp $ -->
22

33
<chapter Id="runtime">
44
<title>Operating System Environment</title>
@@ -1258,8 +1258,10 @@ Out of Memory: Killed process 12345 (postgres).
12581258
kernel's behavior so that it will not <quote>overcommit</> memory.
12591259
Although this setting will not prevent the OOM killer from
12601260
invoking altogether, it will lower the chances significantly and
1261-
will therefore lead to more robust system behavior. This is done
1262-
by selecting strict overcommit mode via <command>sysctl</command>:
1261+
will therefore lead to more robust system behavior. (It might also
1262+
cause fork() to fail when the machine appears to have available
1263+
memory.) This is done by selecting strict overcommit mode via
1264+
<command>sysctl</command>:
12631265
<programlisting>
12641266
sysctl -w vm.overcommit_memory=2
12651267
</programlisting>

0 commit comments

Comments
 (0)