pgsql: doc: Correct the description of server behavior after an OOM kil

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

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(at)gmail(dot)com>
Reviewed-by: Manuel Reyes Bravo <manuelreyesbravo(at)gmail(dot)com>
Reviewed-by: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Discussion: https://postgr.es/m/ce269321-a7f4-48f4-a9ca-a4a4983b9fd6@gmail.com
Backpatch-through: 14

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/14904052e653df8c9d7504c1c3425f0f5e8df04a

Modified Files
--------------
doc/src/sgml/runtime.sgml | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)