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 | c40bb11559c516c24ff1460e2fac5da20abfeb39 (patch) | |
| tree | 083940ce28c5211a7a5247908f6ad2cf69d0713e /src/backend/access/gist/gistvacuum.c | |
| parent | 3aa233f82fad7ba46c93045408d2052ab1450e15 (diff) | |
| download | postgresql-c40bb11559c516c24ff1460e2fac5da20abfeb39.tar.gz postgresql-c40bb11559c516c24ff1460e2fac5da20abfeb39.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/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions