Add PostgreSQL database support #1238
Open
Conversation
This file contains 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.
This PR adds support for using the PostgreSQL database as a storage backend for Krill in preparation for supporting fail-over scenarios for higher availability.
The PR integrates the storage abstraction previously implemented via the kvx crate back into Krill to allow a tight coupling of storage primitives with Krill’s requirements.
We have opted to not move the storage code to async functions as proposed in #1152. We think that storage should generally be fast enough that the gain from using async isn’t all that big. Using a thread pool and sync functions makes it easier to reason about what’s going on and should keep the code simpler.