-
- Downloads
"...postgres-lambda-diff.git" did not exist on "dc3eb5638349e74a6628130a5101ce866455f4a3"
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
Showing
- src/backend/access/transam/xlog.c 24 additions, 8 deletionssrc/backend/access/transam/xlog.c
- src/backend/access/transam/xlogutils.c 43 additions, 20 deletionssrc/backend/access/transam/xlogutils.c
- src/include/access/xlog.h 2 additions, 0 deletionssrc/include/access/xlog.h
- src/include/access/xlogutils.h 1 addition, 0 deletionssrc/include/access/xlogutils.h
Loading
Please register or sign in to comment