summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian2007-12-16 11:24:25 +0000
committerBruce Momjian2007-12-16 11:24:25 +0000
commit7b618017fdd99dafe26c6aaf107123c260ccad9e (patch)
tree8ecc027858fa5decbc6a7b2dfb9344259ba776d4 /doc/src
parente5a9ef55ef475887fd1b697db821a3899fd6cadb (diff)
Update OOM wording.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/runtime.sgml7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 13b3879b88d..ead886f4232 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