Add hook for exec_simple_query and support self-defined spilling memory threshold in cost module. #447
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
|
|
my-ship-it
approved these changes
Jun 4, 2024
Enable setting larger spill mem threshold for optimizer. Signed-off-by: Dongxiao Song <[email protected]> Co-authored-by: wuyifan <[email protected]>
my-ship-it
approved these changes
Jun 6, 2024
foreyes
pushed a commit
to foreyes/cloudberrydb
that referenced
this pull request
Jul 8, 2024
Enable setting larger spill mem threshold for optimizer. Add hook for exec_simple_query Add guc optimizer_spilling_mem_threshold to support self-defined spilling memory threshold in cost module. Signed-off-by: Dongxiao Song <[email protected]> Co-authored-by: wuyifan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Change logs
Why are the changes needed?
Support more flexible extension.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Tested by CI and tpcds.