aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-08-31 08:52:13 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-08-31 08:52:13 -0400
commit3fc489cb36a53bc246271107450c5cf5fcd5b009 (patch)
treecf921e677c8d81156d3d86f1e4c67d31d473afe6 /src/backend/access/gist/gistxlog.c
parenta66be67820063dc3d880b2a5408714b877eec8ae (diff)
downloadpostgresql-3fc489cb36a53bc246271107450c5cf5fcd5b009.tar.gz
postgresql-3fc489cb36a53bc246271107450c5cf5fcd5b009.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/gistxlog.c')
0 files changed, 0 insertions, 0 deletions