On Wed, Jan 12, 2022 at 01:10:25PM +0900, Michael Paquier wrote:
>
> xlog.c can be a good read to check the assumptions WAL replay relies
> on, with things like CheckRecoveryConsistency() or
> reachedConsistency.
That should only stand for a WAL expected to be missing right? For something
unexpected it should fail in XLogReadRecord() when trying to fetch a missing
block?