feat: Do not hardcode orioledb.main_buffers in postgresql.conf - #2365
Open
za-arthur wants to merge 1 commit into
Open
feat: Do not hardcode orioledb.main_buffers in postgresql.conf#2365za-arthur wants to merge 1 commit into
orioledb.main_buffers in postgresql.conf#2365za-arthur wants to merge 1 commit into
Conversation
supabase-admin-api now stores orioledb config into `generated-optimizations.conf` config file and therefore we should avoid hardcoding `orioledb.main_buffers` into `postgresql.conf`
za-arthur
force-pushed
the
artur/no_hardcoded_orioledb_config
branch
from
August 14, 2026 13:52
6d774a7 to
e70a1ab
Compare
mmlb
approved these changes
Aug 14, 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.
What kind of change does this PR introduce?
supabase-admin-apinow stores orioledb config intogenerated-optimizations.confconfig file and therefore we should avoid hardcodingorioledb.main_buffersintopostgresql.confhttps://linear.app/supabase/issue/ORI-219/apply-orioledb-guc-settings-based-on-instance-size
What is the current behavior?
Now
ansible/files/postgres_prestart.sh.j2hardcodesorioledb.main_buffersintopostgresql.confWhat is the new behavior?
supabase-admin-apiwill save optimized config for orioledb intogenerated-optimizations.conf.Additional context
https://linear.app/supabase/issue/ORI-219/apply-orioledb-guc-settings-based-on-instance-size