Bump redb from 2.1.1 to 2.1.2

[dependabot[bot]]

Bumps redb from 2.1.1 to 2.1.2.

Release notes

Sourced from redb's releases.

2.1.2

Major fixes:

• Fix leak of database space that could occur when calling restore_savepoint()
• Fix leak of database space when calling delete_multimap_table()
• Fix database corruption which could occur when restoring a savepoint. This edge case is rare, and could only occur if the database was less than approximately 4TiB when the savepoint was created, and greater than 4TiB when the savepoint was restored
• Fix edge case where a transient I/O error that occurred during transaction commit, but then did not reoccur when the Database was dropped, could cause database corruption

Important: If your application has called restore_savepoint(), delete_multimap_table(), or you suspect it may have experienced a transient I/O error during transaction commit. It is recommended that you run check_integrity() after upgrading to this version. This will both detect corruption and clean up any leaked space.

Other changes and fixes:

• Optimize page freeing to reduce the size of the database file
• Fix several cases where check_integrity() would return Ok(false) instead of Ok(true)
• Fix some cases where compact() did not fully compact the database
• Make the metadata overhead returned by WriteTransaction::stats() more accurate
• Return StorageError::ValueTooLarge when a key-value pair exceeds a total of 3.75GiB. Previously, a panic would occur for key-value pairs that were approximately 4GiB.
• Downgrade several info! log messages to debug!
• Improve documentation

Changelog

Sourced from redb's changelog.

2.1.2 - 2024-08-25

Major fixes:

• Fix leak of database space that could occur when calling restore_savepoint()
• Fix leak of database space when calling delete_multimap_table()
• Fix database corruption which could occur when restoring a savepoint. This edge case is rare, and could only occur if the database was less than approximately 4TiB when the savepoint was created, and greater than 4TiB when the savepoint was restored
• Fix edge case where a transient I/O error that occurred during transaction commit, but then did not reoccur when the Database was dropped, could cause database corruption

Important: If your application has called restore_savepoint(), delete_multimap_table(), or you suspect it may have experienced a transient I/O error during transaction commit. It is recommended that you run check_integrity() after upgrading to this version. This will both detect corruption and clean up any leaked space.

Other changes and fixes:

• Optimize page freeing to reduce the size of the database file
• Fix several cases where check_integrity() would return Ok(false) instead of Ok(true)
• Fix some cases where compact() did not fully compact the database
• Make the metadata overhead returned by WriteTransaction::stats() more accurate
• Return StorageError::ValueTooLarge when a key-value pair exceeds a total of 3.75GiB. Previously, a panic would occur for key-value pairs that were approximately 4GiB.
• Downgrade several info! log messages to debug!
• Improve documentation

Commits

• 4dbd9cd Bump version to 2.1.2
• 3967230 Update author's email address
• e47e7d4 Update changelog
• 072c81c Improve compaction
• 0d94695 Compact subtrees of multimap tables
• 91d4ee1 Better markdown benchmarks (#849)
• ea41b5e Refactor InternalTableDefinition
• fe0450c Add test for multithreaded reads of a Table
• c93a74a chore: use heed for LMDB in benchmark (#847)
• 7a35233 Add check_integrity() to fuzzer
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot[bot]]

Superseded by #1222.