mirror of
https://github.com/postgres/postgres.git
synced 2026-02-15 08:37:56 -05:00
Ordinarily, a failure (unexpected exit status) of the startup subprocess
should be considered fatal, so the postmaster should just close up shop
and quit. However, if we sent the startup process a SIGQUIT or SIGKILL
signal, the failure is hardly "unexpected", and we should attempt restart;
this is necessary for recovery from ordinary backend crashes in hot-standby
scenarios. I attempted to implement the latter rule with a two-line patch
in commit
|
||
|---|---|---|
| .. | ||
| autovacuum.c | ||
| bgwriter.c | ||
| checkpointer.c | ||
| fork_process.c | ||
| Makefile | ||
| pgarch.c | ||
| pgstat.c | ||
| postmaster.c | ||
| startup.c | ||
| syslogger.c | ||
| walwriter.c | ||