aboutsummaryrefslogtreecommitdiff
path: root/src/include/postgres.h
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-12-02 10:49:54 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2011-12-02 10:49:54 +0200
commit1e616f639156b2431725f7823c999486ca46c1ea (patch)
treef8e2cbade787fb90a73f68c3f9a9ff8fa03d9cd1 /src/include/postgres.h
parent15a5006aac1432da35ff6a7ae27a018ed300e860 (diff)
downloadpostgresql-1e616f639156b2431725f7823c999486ca46c1ea.tar.gz
postgresql-1e616f639156b2431725f7823c999486ca46c1ea.zip
During recovery, if we reach consistent state and still have entries in the
invalid-page hash table, PANIC immediately. Immediate PANIC is much better than waiting for end-of-recovery, which is what we did before, because the end-of-recovery might not come until months later if this is a standby server. Also refrain from creating a restartpoint if there are invalid-page entries in the hash table. Restarting recovery from such a restartpoint would not see the invalid references, and wouldn't be able to cross-check them when consistency is reached. That wouldn't matter when things are going smoothly, but the more sanity checks you have the better. Fujii Masao
Diffstat (limited to 'src/include/postgres.h')
0 files changed, 0 insertions, 0 deletions