-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Provide callback when tasks are starting / stopping #16451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -247,7 +247,7 @@ void AttachedDatabase::Close() { | |||
} | |||
CheckpointOptions options; | |||
options.wal_action = CheckpointWALAction::DELETE_WAL; | |||
storage->CreateCheckpoint(options); | |||
storage->CreateCheckpoint(nullptr, options); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only place where we're missing out on a ClientContext, which I think is fine though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! LGTM - could you just look at the CI failure?
Thanks, fixed :) |
Thanks! |
Provide callback when tasks are starting / stopping (duckdb/duckdb#16451) [tests] Add allow_unsigned_extensions require (duckdb/duckdb#16499)
Follow-up to #16451 that fixes the situation where checkpoint / vacuum tasks would not be correctly identified as belonging to a given query / transaction because the ClientContext wasn't correctly set.
This allows extensions to do further instrumentation around tasks, e.g. install a custom thread context.