Skip to content

fix(studio): use postgres user for read write operations#4828

Merged
sweatybridge merged 1 commit intosupabase:developfrom
singh-inder:fix/studio-user
Feb 9, 2026
Merged

fix(studio): use postgres user for read write operations#4828
sweatybridge merged 1 commit intosupabase:developfrom
singh-inder:fix/studio-user

Conversation

@singh-inder
Copy link
Contributor

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

studio sends its own connection string to pgmeta for executing queries via studio sql-editor. It defaults to supabase_admin user. https://github.com/supabase/supabase/blob/18cc6f8fe9654e0b682d4f6564adc838977d197e/apps/studio/lib/api/self-hosted/constants.ts#L8

What is the new behavior?

Use postgres user for studio read write operations

@singh-inder singh-inder requested a review from a team as a code owner February 9, 2026 08:15
@coveralls
Copy link

Pull Request Test Coverage Report for Build 21817338223

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • 5 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.02%) to 57.84%

Files with Coverage Reduction New Missed Lines %
internal/gen/keys/keys.go 5 12.9%
Totals Coverage Status
Change from base Build 21817171276: -0.02%
Covered Lines: 7455
Relevant Lines: 12889

💛 - Coveralls

@sweatybridge sweatybridge merged commit ce89d32 into supabase:develop Feb 9, 2026
14 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants