FATAL: lock file "postmaster.pid" already exists — Is another postmaster running in data directory?
PostgreSQL won’t start because a stale postmaster.pid file remains (or another instance really is running).
lock file "postmaster.pid" already existsIs another postmaster Meaning
After a crash or unclean shutdown (common with Homebrew on macOS), the PID file stays behind.
Common causes
- Unclean shutdown/crash
- Another PostgreSQL instance using the same data directory
⚡ Quick fix
- Make sure no postgres process is running (ps aux | grep postgres)
- Then delete the stale postmaster.pid and start again
Detailed fix by platform
Linux
brew services stop postgresql@16 && rm /opt/homebrew/var/postgresql@16/postmaster.pid && brew services start postgresql@16
How to diagnose
- Process — Is postgres running?
- PID — Does the PID in the file exist?
🔧 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
- prepared statement exists ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
- 23505 PostgreSQL: ERROR: duplicate key value violates unique constraint
- 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.
Report a correction or suggest an improvement
Last updated 13 Oct 2026