diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-02-06 15:29:26 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-02-06 15:29:41 -0500 |
| commit | ef19c9dfaa99a2b78ed0f78aa4a44ed31636fdc4 (patch) | |
| tree | 18faa1f2c0139ded2b8f3564b208dfd2c0b84010 /src/backend/access/gist/gist.c | |
| parent | c74ad4e55bf9142478192e5507555ac2c95e0985 (diff) | |
| download | postgresql-ef19c9dfaa99a2b78ed0f78aa4a44ed31636fdc4.tar.gz postgresql-ef19c9dfaa99a2b78ed0f78aa4a44ed31636fdc4.zip | |
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.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions