[DO NOT MERGE] feat: Do not hardcode orioledb.main_buffers in postgresql.conf - #2365
Draft
za-arthur wants to merge 1 commit into
Draft
[DO NOT MERGE] 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
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
orioledb.main_buffers in postgresql.conforioledb.main_buffers in postgresql.conf
za-arthur
marked this pull request as draft
August 17, 2026 10:10
za-arthur
force-pushed
the
artur/no_hardcoded_orioledb_config
branch
3 times, most recently
from
August 17, 2026 11:12
765457d to
d8c5c4a
Compare
PostgreSQL Extension Dependency Analysis: PR #2365
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension Dependencies |
This comment has been minimized.
This comment has been minimized.
za-arthur
force-pushed
the
artur/no_hardcoded_orioledb_config
branch
2 times, most recently
from
August 18, 2026 19:47
2b67b13 to
fac9032
Compare
mmlb
force-pushed
the
artur/no_hardcoded_orioledb_config
branch
from
August 18, 2026 19:50
fac9032 to
db9e418
Compare
PostgreSQL Package Dependency Analysis: PR #2365
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
mmlb
force-pushed
the
artur/no_hardcoded_orioledb_config
branch
from
August 18, 2026 21:09
db9e418 to
5948fda
Compare
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 19, 2026 12:20
5948fda to
67d16b3
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
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