FATAL: role "x" does not exist
PostgreSQL has no login role with that name.
Exact message you may see
role does not exist
Seen on:
PostgreSQL
Meaning
psql defaults to your OS username as the role. Fresh installs only have postgres; Homebrew installs create a role named after your macOS user.
Common causes
- Connecting without -U (defaults to OS user)
- Role never created
- Docker image created a different POSTGRES_USER
⚡ Quick fix
- Connect as an existing role: psql -U postgres
- Create the role: CREATE ROLE app LOGIN PASSWORD '…'
- Check docker env POSTGRES_USER
Detailed fix by platform
PostgreSQL
sudo -u postgres createuser --interactive --pwprompt app
How to diagnose
- Role — Which name?
- Roles — \du lists?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PostgreSQL
- 23505 PostgreSQL: ERROR: duplicate key value violates unique constraint
- prepared statement exists ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
- incompatible data directory FATAL: database files are incompatible with server — The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026