Correctly use a lock when accessing the EncryptionKeyManager #19772
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
2 tasks
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Nov 26, 2025
Correctly use a lock when accessing the EncryptionKeyManager (duckdb/duckdb#19772) Remove httpfs patches and bump (duckdb/duckdb#19763)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Nov 26, 2025
Correctly use a lock when accessing the EncryptionKeyManager (duckdb/duckdb#19772) Remove httpfs patches and bump (duckdb/duckdb#19763) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #19754
When attaching encrypted databases in parallel through different connections we can access the encryption key cache in parallel, so we need a lock.