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

Improve wording.

Browse Source
This commit is contained in:
Alvaro Herrera 2007-12-17 13:48:31 +00:00
parent 3791d26d4b
commit 048f69e242
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.389 2007/12/16 11:24:25 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.390 2007/12/17 13:48:31 alvherre Exp $ -->
<chapter Id="runtime"> <chapter Id="runtime">
<title>Operating System Environment</title> <title>Operating System Environment</title>
@ -1257,10 +1257,11 @@ Out of Memory: Killed process 12345 (postgres).
On Linux 2.6 and later, an additional measure is to modify the On Linux 2.6 and later, an additional measure is to modify the
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 being invoked altogether, it will lower the chances significantly and
will therefore lead to more robust system behavior. (It might also will therefore lead to more robust system behavior. (It might also
cause fork() to fail when the machine appears to have available memory cause <function>fork()</> to fail when the machine appears to have
because of other applications with careless memory allocation.) This available memory but it is actually reserved
to other applications with careless memory allocation.) This
is done by selecting strict overcommit mode via is done by selecting strict overcommit mode via
<command>sysctl</command>: <command>sysctl</command>:
<programlisting> <programlisting>