Fix shadow pg wal replay - #26
Merged
Merged
Conversation
harshil-goel
force-pushed
the
harshil/fix-shadow-wal-issue
branch
from
June 18, 2026 09:21
f6d395d to
5eb900b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Under backpressure in walshadow, the shadow pg connection is closed. When it tries to come back, it will read the WAL from out/. However the out/ directory is only written to after the entire block is written. We fix that by streaming the unwritten wal when the shadow pg tries to come back.
Fixes #23