Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commite5a9ef5

Browse files
committed
Add docs about OOM killer.
lst_hoe01@kwsoft.de
1 parent3e4c6b5 commite5a9ef5

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.387 2007/12/1610:17:13 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.388 2007/12/1611:22:33 momjian Exp $ -->
22

33
<chapter Id="runtime">
44
<title>Operating System Environment</title>
@@ -1258,8 +1258,10 @@ Out of Memory: Killed process 12345 (postgres).
12581258
kernel's behavior so that it will not <quote>overcommit</> memory.
12591259
Although this setting will not prevent the OOM killer from
12601260
invoking altogether, it will lower the chances significantly and
1261-
will therefore lead to more robust system behavior. This is done
1262-
by selecting strict overcommit mode via <command>sysctl</command>:
1261+
will therefore lead to more robust system behavior. (It might also
1262+
cause fork() to fail when the machine appears to have available
1263+
memory.) This is done by selecting strict overcommit mode via
1264+
<command>sysctl</command>:
12631265
<programlisting>
12641266
sysctl -w vm.overcommit_memory=2
12651267
</programlisting>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp