Repository navigation
feat(wal): retire closed source payloads while retaining retry receipts - #416
Merged
beinan merged 1 commit intoOct 20, 2026
Merged
Conversation
40 of 47 tasks
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
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.
Summary
After a verified publication closes its selected source prefix, release those accepted-record slots and omit the retired bodies from new WAL checkpoints. Keep each producer lane's latest receipt and retirement boundary so an exact retry after restart returns its original ACK. Other tables and unpublished suffixes remain retained.
Checkpoint format v9 validates retained sequence continuity and encodes each retirement boundary in a fixed 52-byte frame. Previously captured checkpoints keep their payload ownership. Physical log/image collection and catalog advancement remain separate work.
Refs #378.
Testing