From 7b618017fdd99dafe26c6aaf107123c260ccad9e Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 16 Dec 2007 11:24:25 +0000
Subject: [PATCH] Update OOM wording.

---
 doc/src/sgml/runtime.sgml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 13b3879b88..ead886f423 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.388 2007/12/16 11:22:33 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.389 2007/12/16 11:24:25 momjian Exp $ -->
 
 <chapter Id="runtime">
  <title>Operating System Environment</title>
@@ -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
     <command>sysctl</command>:
 <programlisting>
 sysctl -w vm.overcommit_memory=2
-- 
2.11.0