pgsql: Fix postmaster to attempt restart after a hot-standby crash. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix postmaster to attempt restart after a hot-standby crash.
Date
Msg-id E1RuVCq-0007qX-SU@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix postmaster to attempt restart after a hot-standby crash.

The postmaster was coded to treat any unexpected exit of the startup
process (i.e., the WAL replay process) as a catastrophic crash, and not try
to restart it. This was OK so long as the startup process could not have
any sibling postmaster children.  However, if a hot-standby backend
crashes, we SIGQUIT the startup process along with everything else, and the
resulting exit is hardly "unexpected".  Treating it as such meant we failed
to restart a standby server after any child crash at all, not only a crash
of the WAL replay process as intended.  Adjust that.  Back-patch to 9.0
where hot standby was introduced.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/cc0f6fff1a0dd44d5481836154ac3639be0c056f

Modified Files
--------------
src/backend/postmaster/postmaster.c |   13 +++++++++----
1 files changed, 9 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Michael Meskes
Date:
Subject: pgsql: Allow the connection keyword array to carry all seven items in e
Next
From: Tom Lane
Date:
Subject: pgsql: Fix postmaster to attempt restart after a hot-standby crash.