diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-31 08:52:13 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-08-31 08:52:13 -0400 |
| commit | e3439a45546a81e8af4a2b11931f5a0b5404c5b6 (patch) | |
| tree | 13d1a9c94f04ce317a0c5ddf0a3e562daaa4fdaa /src/backend/access/gist/gist.c | |
| parent | 934630cd8e51967dfc70c932f6a7fb7fb8a53475 (diff) | |
| download | postgresql-e3439a45546a81e8af4a2b11931f5a0b5404c5b6.tar.gz postgresql-e3439a45546a81e8af4a2b11931f5a0b5404c5b6.zip | |
Prevent starting a standalone backend with standby_mode on.
This can't really work because standby_mode expects there to be more
WAL arriving, which there will not ever be because there's no WAL
receiver process to fetch it. Moreover, if standby_mode is on then
hot standby might also be turned on, causing even more strangeness
because that expects read-only sessions to be executing in parallel.
Bernd Helmle reported a case where btree_xlog_delete_get_latestRemovedXid
got confused, but rather than band-aiding individual problems it seems
best to prevent getting anywhere near this state in the first place.
Back-patch to all supported branches.
In passing, also fix some omissions of errcodes in other ereport's in
readRecoveryCommandFile().
Michael Paquier (errcode hacking by me)
Discussion: <00F0B2CEF6D0CEF8A90119D4@eje.credativ.lan>
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions