Add docs about OOM killer.

lst_hoe01@kwsoft.de

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 7e5ff5b275d8d311b69dfe6a04d5ee6428f32a62..1c561c0a1cc5696b2b6544f06e5d94b8344262d0 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1258,8 +1258,10 @@ Out of Memory: Killed process 12345 (postgres).
     kernel's behavior so that it will not <quote>overcommit</> memory.
     Although this setting will not prevent the OOM killer from
     invoking 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>:
+    will therefore lead to more robust system behavior.  (It might also
+    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>
 sysctl -w vm.overcommit_memory=2
 </programlisting>