postgres supabase_admin user not created in initial setup
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- postgres
- Domain
- databases
Research direction
Start with migrations/db/init-scripts/00000000000000-initial-schema.sql and compare the current version with commit ab7f879. Verify the initial database setup creates the supabase_admin role and that a fresh startup with container 15.8.1.020 completes without the missing-role error.
Written by the indexing model from the issue text.
Description
- [ x] I confirm this is a bug with Supabase, not with my own application.
- [ x] I confirm I have searched the [Docs]
Describe the bug
After upgrading db container to 15.8.1.020 database won't startup correctly complaining that supabase_adming role does not exist.
db starts up correctly with container 15.1.1.78
To Reproduce
- Delete all postgres database files
- change db container to 15.8.1.020 & startup your system
System information
I use the container in a kubernetes setup but it looks like a general problem with migrations/db/init-scripts/00000000000000-initial-schema.sql in the most recent commit
ab7f879
the line create user supabase_admin dissapeared (it was present before).
Additional context
- Dominant language
- Nix
- Stars
- 1.8k
- Forks
- 266
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 25
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/postgres
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
`supabase/postgres:17.6.1.105` (amd64) — backend SIGSEGV during a heavy pgTAP file, CI-CPU-specific Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in supabase/postgres
Similar issues
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
[BUG] A column whose default is the empty string is drawn in the ER diagram as having no default Openbug database-provider good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libredb/libredb-studio#1030 · 6 comments ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug redshift
Difficulty 2/5 1-3 hours Newbie friendliness 88/100