Limit the maximum number of vacuum tasks launched during a checkpoint, configurable through max_vacuum_tasks
#13811
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
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Sep 11, 2024
Merge pull request duckdb/duckdb#13811 from Mytherin/vacuumlimit
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Sep 11, 2024
Merge pull request duckdb/duckdb#13811 from Mytherin/vacuumlimit 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
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.
Currently the vacuum tasks do not yet do optimistic writing, which can lead to large memory (or temp disk) usage if many vacuum jobs are performed at once. This should ideally be resolved differently in the future, but this adds a toggle that can limit the impact of this problem.