Refactor shadow WAL to use segments #225
Merged
Conversation
This file contains 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
benbjohnson
force-pushed
the
db-wal-segments
branch
4 times, most recently
from
9e30408 to
6eb2907
Compare
benbjohnson
force-pushed
the
db-wal-segments
branch
from
6eb2907 to
8ff784b
Compare
benbjohnson
force-pushed
the
db-wal-segments
branch
from
8ff784b to
99fe882
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request refactors the shadow WAL to store individual segments instead of simply appending on to WAL files. This provides the ability to transactionally store segments and to separate them along SQLite transaction boundaries. These characteristics are necessary to enable live replication so that the replicas do not need to compute transaction boundaries on every read.
This is a draft pull request and needs additional cleanup and testing.
Fixes #191