pg_dump: error: aborting because of server version mismatch
Your pg_dump client is older than the server you’re dumping.
Exact message you may see
aborting because of server version mismatchserver version: 16
Seen on:
PostgreSQL
Meaning
pg_dump must be the same major version or newer than the server. Ubuntu’s default client lags behind managed servers (RDS, Supabase).
Common causes
- Old postgresql-client package
- Multiple versions installed, older one first on PATH
⚡ Quick fix
- Install the matching client (apt install postgresql-client-16 from the PGDG repo)
- Call the versioned binary directly
- Run pg_dump inside a postgres:16 container
Detailed fix by platform
Docker
docker run --rm postgres:16 pg_dump "$DATABASE_URL" > dump.sql
How to diagnose
- Versions — pg_dump --version vs SELECT version()
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 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.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 14 Oct 2026