From d51045fad5a7ecddd5e4f3fef632ef7dbaa7508d Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sun, 16 Dec 2007 11:24:25 +0000 Subject: [PATCH] Update OOM wording. --- doc/src/sgml/runtime.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 1c561c0a1c..2cb9ad99f2 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1259,8 +1259,9 @@ Out of Memory: Killed process 12345 (postgres). 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. (It might also - cause fork() to fail when the machine appears to have available - memory.) This is done by selecting strict overcommit mode via + cause fork() to fail when the machine appears to have available memory + because of other applications with careless memory allocation.) This + is done by selecting strict overcommit mode via sysctl: sysctl -w vm.overcommit_memory=2 -- 2.39.5