database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00
Code Activity

doc: Correct the description of server behavior after an OOM kill

Browse Source 
The documentation stated that existing connections would continue to
function normally after the OOM killer terminated the postmaster.
In fact, those connections eventually terminate when server processes
detect the postmaster's death.

Clarify that the OOM killer can terminate either the postmaster or a
child process. If the postmaster is killed, the server must be restarted.
If a child process is killed, PostgreSQL typically terminates the
remaining connections and either recovers automatically or shuts down,
depending on restart_after_crash.

Backpatch to all supported versions.

Author: Takeshi Ideriha <iderihatakeshi@gmail.com>
Reviewed-by: Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/ce269321-a7f4-48f4-a9ca-a4a4983b9fd6@gmail.com
Backpatch-through: 14
This commit is contained in:
Fujii Masao
2026-10-16 22:42:40 +09:00
parent 707b3738df
commit dfbc1507cd
1 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1325,10 +1325,10 @@ default:\
The default virtual memory behavior on Linux is not The default virtual memory behavior on Linux is not
optimal for <productname>PostgreSQL</productname>. Because of the optimal for <productname>PostgreSQL</productname>. Because of the
way that the kernel implements memory overcommit, the kernel might way that the kernel implements memory overcommit, the kernel might
terminate the <productname>PostgreSQL</productname> postmaster (the terminate a <productname>PostgreSQL</productname> server process,
supervisor server process) if the memory demands of either including the postmaster (the supervisor server process), if the memory
<productname>PostgreSQL</productname> or another process cause the demands of either <productname>PostgreSQL</productname> or another process
system to run out of virtual memory. cause the system to run out of virtual memory.
</para> </para>
<para> <para>
@@ -1340,9 +1340,15 @@ Out of Memory: Killed process 12345 (postgres).
</programlisting> </programlisting>
This indicates that the <filename>postgres</filename> process This indicates that the <filename>postgres</filename> process
has been terminated due to memory pressure. has been terminated due to memory pressure.
Although existing database connections will continue to function If the postmaster is terminated, all connections will eventually be
normally, no new connections will be accepted. To recover, terminated. To recover, <productname>PostgreSQL</productname> will
<productname>PostgreSQL</productname> will need to be restarted. need to be restarted.
If a child process is terminated, <productname>PostgreSQL</productname> will
typically terminate all remaining connections and either recover
automatically, if
<link linkend="guc-restart-after-crash"><varname>restart_after_crash</varname></link>
is enabled, or shut down. If <productname>PostgreSQL</productname> shuts
down, it will need to be restarted to recover.
</para> </para>
<para> <para>