-
Notifications
You must be signed in to change notification settings - Fork 294
Closed
Description
Describe the bug
Supabase db diff commands after db pull command with supabase_admin user aren’t executing due to permission issues .
To Reproduce
i added cli command and output in screenshot section
Expected behavior
The successful execution of the supabase db pull command and the proper creation of the SQL file.
Screenshots
sysmgr@aidev:~/supabase/docker$ DB_URL='postgres://supabase_admin:qwer1234@localhost:7654/postgres'
sysmgr@aidevapp01:~/supabase-proj$ npx supabase db pull --db-url $DB_URL --schema public --debug
sysmgr@aidev:~/supabase-proj$ npx supabase db diff --create-ticket --db-url $DB_URL
Connecting to remote database...
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Applying migration 20250707070841_remote_schema.sql...
ERROR: must be able to SET ROLE "supabase_admin" (SQLSTATE 42501)
At statement: 13
ALTER SCHEMA "pgmq_public" OWNER TO "supabase_admin"
Try rerunning the command with --debug to troubleshoot the error.
Sent crash report: 3e6a15d6cd994f40baf68b9a678a32d3
Quote the crash ID above when filing a bug report: https://github.com/supabase/cli/issues/new/choose
System information
Rerun the failing command with --create-ticket
flag.
- Ticket ID: 3e6a15d6cd994f40baf68b9a678a32d3
- Version of OS: Ubuntu 22.04
- Version of CLI: v2.30.4
Self hosting Module Versions
PostgreSQL: supabase/postgres:15.8.1.049
PostgREST: postgrest/postgrest:v12.2.8
- Storage API: supabase/storage-api:v1.19.3
- Kong Gateway: kong:2.8.1
- Supavisor (Connection Pooler): supabase/supavisor:2.4.12
- Realtime: supabase/realtime:v2.34.40
- Studio: supabase/studio:20250224-d10db0f
- Postgres Meta: supabase/postgres-meta:v0.86.1
- Auth (GoTrue): supabase/gotrue:v2.170.0
- Edge Functions: supabase/edge-runtime:v1.67.2
- Logflare: supabase/logflare:1.12.0
- ImgProxy: darthsim/imgproxy:v3.8.0
- Vector (Log Router): timberio/vector:0.28.1-alpine
Metadata
Metadata
Assignees
Labels
No labels