Remove succssor field from block sideband#5038
Open
RickiNano wants to merge 2 commits intonanocurrency:developfrom
Open
Remove succssor field from block sideband#5038RickiNano wants to merge 2 commits intonanocurrency:developfrom
RickiNano wants to merge 2 commits intonanocurrency:developfrom
Conversation
Test Results for Commit 7a1d517Pull Request 5038: Results Test Case Results
Last updated: 2026-02-28 21:46:54 UTC |
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.
This V26 database migration rewrites all blocks to remove the 32-byte successor field from block. The successor data has already been copied to the successor table in migration V24
Serialize_v25, deserialize_v25 and size_v25 methods has been added to block_sideband to preserve the ability to read the legacy format during migrations
The migration uses cursor-based iteration with short-lived read transactions to prevent LMDB database bloat during migration.
From my testing, ledger db size increased by only one gb during migration