Let resource limits (threads + memory) be overridable#31
Merged
slinjhu merged 1 commit intoMay 6, 2026
Merged
Conversation
slinjhu
approved these changes
May 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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, it's not possible to override or set memory or thread limits per DuckDB connection. For S3 queries, it's apparently hardcoded to S3 through a
memory_limitparameter which isn't exposed anywhere (AFAIS).Since the resource limits anyways should have higher relevance when
smoosenseis used in a hosted/server-side context, I decided to let this be configurable with env-vars instead, and also for all connection types, not just S3 ones.