recovery: make LSN gap check more thorough
Currently, the lsn gap check is rather sloppy: when we open an xlog file for recovery, we check that its vclock equals the vclock of the last replayed row (see recover_remaining_wals), so if there were WAL write errors at the end of an xlog file, we will report a false-positive gap error (because wal doesn't rollback lsn counter). Let's use PrevVclock xlog meta key introduced earlier to improve the check.
Please register or sign in to comment