mirror of
https://github.com/postgres/postgres.git
synced 2025-07-09 22:41:56 +03:00
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
This commit is contained in:
@ -190,6 +190,8 @@ typedef enum
|
||||
|
||||
extern XLogRecPtr XactLastRecEnd;
|
||||
|
||||
extern bool reachedMinRecoveryPoint;
|
||||
|
||||
/* these variables are GUC parameters related to XLOG */
|
||||
extern int CheckPointSegments;
|
||||
extern int wal_keep_segments;
|
||||
|
Reference in New Issue
Block a user