From 2367c60c0a40bba5e1d9b8cd714dabce8ed93f13 Mon Sep 17 00:00:00 2001
From: Takeshi Ideriha <iderihatakeshi@gmail.com>
Date: Thu, 8 Oct 2026 10:40:20 +0900
Subject: [PATCH v3] Fix explain how postgres behaves when an OOM killer is
 invoked.

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

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index d9984910cc4..7db6bc7d1a5 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1359,9 +1359,15 @@ Out of Memory: Killed process 12345 (postgres).
 </programlisting>
     This indicates that the <filename>postgres</filename> process
     has been terminated due to memory pressure.
-    Although existing database connections will continue to function
-    normally, no new connections will be accepted.  To recover,
-    <productname>PostgreSQL</productname> will need to be restarted.
+    If the postmaster is terminated, all connections will eventually be
+    terminated.  To recover, <productname>PostgreSQL</productname> will
+    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>
-- 
2.50.1 (Apple Git-155)