---------------

When the WAL replay in startup process has reached the end of archived WAL,

recoverable usingrecovery_command, it starts up the walreceiver process

restorable usingrestore_command, it starts up the walreceiver process

to fetch more WAL (if streaming replication is configured).

Walreceiver is a postmaster subprocess, so the startup process can't fork it