feat: Bump admin-api to 0.114.0 - #2342
Open
za-arthur wants to merge 1 commit into
Open
Conversation
imor
approved these changes
Aug 4, 2026
za-arthur
force-pushed
the
artur/optimized_orioledb_config
branch
2 times, most recently
from
August 4, 2026 12:50
f863a32 to
2f721de
Compare
admin-api 0.114.0 contains optimized orioledb config feature according to the worksheet https://linear.app/supabase/issue/ORI-119/orioledb-variable-guc-settings-depending-on-ec2-size
za-arthur
force-pushed
the
artur/optimized_orioledb_config
branch
from
August 4, 2026 14:48
2f721de to
4487d6f
Compare
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.
What kind of change does this PR introduce?
admin-api
0.114.0contains optimized orioledb config feature according to the worksheethttps://linear.app/supabase/issue/ORI-119/orioledb-variable-guc-settings-depending-on-ec2-size
What is the current behavior?
Currently the optimizer sets only orioledb.recovery_idx_pool_size, orioledb.recovery_pool_size options.
What is the new behavior?
The optimizer sets additional orioledb configs.
Additional context
https://linear.app/supabase/issue/ORI-219/apply-orioledb-guc-settings-based-on-instance-size