Runtime : Detach duckdb files with tx
lock
#4590
Merged
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.
Details here :
duckdb/duckdb#9342
duckdb/duckdb#11297
Even though we don't run any
ATTACH
&DETACH
in parallel but I think that duckDB is also getting into this condition when running any information_schema call in parallel to DETACH operation.We ensure all
DETACH
happen in isolation and sequentially using internal driverstx
lock.