database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Add docs about OOM killer.

Browse Source 
lst_hoe01@kwsoft.de
This commit is contained in:
Bruce Momjian 2007-12-16 11:22:33 +00:00
parent 3e4c6b5422
commit e5a9ef55ef
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.387 2007/12/16 10:17:13 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.388 2007/12/16 11:22:33 momjian Exp $ -->
<chapter Id="runtime"> <chapter Id="runtime">
<title>Operating System Environment</title> <title>Operating System Environment</title>
@ -1258,8 +1258,10 @@ Out of Memory: Killed process 12345 (postgres).
kernel's behavior so that it will not <quote>overcommit</> memory. kernel's behavior so that it will not <quote>overcommit</> memory.
Although this setting will not prevent the OOM killer from Although this setting will not prevent the OOM killer from
invoking altogether, it will lower the chances significantly and invoking altogether, it will lower the chances significantly and
will therefore lead to more robust system behavior. This is done will therefore lead to more robust system behavior. (It might also
by selecting strict overcommit mode via <command>sysctl</command>: cause fork() to fail when the machine appears to have available
memory.) This is done by selecting strict overcommit mode via
<command>sysctl</command>:
<programlisting> <programlisting>
sysctl -w vm.overcommit_memory=2 sysctl -w vm.overcommit_memory=2
</programlisting> </programlisting>