ERROR: column "x" of relation "y" already exists
ALTER TABLE ADD COLUMN for a column that’s already there.
Exact message you may see
column already exists
Seen on:
PostgreSQL
Meaning
Usually a migration applied twice or manual schema changes.
Common causes
- Migration re-run
- Manual change not reflected in migrations
⚡ Quick fix
- Use ADD COLUMN IF NOT EXISTS
- Reconcile migration history
Detailed fix by platform
PostgreSQL
ALTER TABLE users ADD COLUMN IF NOT EXISTS last_login timestamptz;
How to diagnose
- Column — Already present (\d table)?
- 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
- 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
- 57014 ERROR: canceling statement due to statement timeout
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