feat: upgrade redb to v3 compatible format #69
Merged
Conversation
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
|
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-docs/pr/69/docs/iroh_docs/ Last updated: 2025-10-14T10:23:47Z |
dignifiedquire
approved these changes
Sep 30, 2025
Contributor
|
@Frando can we get this in? |
Frando
force-pushed
the
Frando/upgrade-redb-format
branch
from
d91181f to
95c7d72
Compare
Member
Author
|
rebased |
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.
Description
The recently released redb v3 has incompatible changes to the database format. The recommended upgrade procedure is to upgrade the database with
Database::upgradeon redb v2.6+. The upgrade has to be done on redb v2, not v3. See https://github.com/cberner/redb/blob/master/CHANGELOG.md#removes-support-for-file-format-v2.This updates redb to 2.6 and performs the upgrade when opening the database. Calling upgrade on an already upgraded database is a no-op.
With this merged in the next release, we can then update redb to v3 in the version after.
Breaking Changes
Notes & open questions
Change checklist