[POSIX] Add ability to configure BadgerDB#918
Merged
AlCutter merged 1 commit intotransparency-dev:mainfrom Mar 26, 2026
Merged
Conversation
mhutchinson
approved these changes
Mar 25, 2026
phbnf
approved these changes
Mar 25, 2026
AlCutter
force-pushed
the
badger_badger_badger
branch
from
3cd2c1c to
594685f
Compare
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
3 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 PR exposes the ability to configure the BadgerDB instance which underlies the POSIX antispam implementation.
This gives the user of the library latitude to tweak performance related parameters based on parameters of their expected use-case.