ERROR: relation "x" already exists
CREATE TABLE/INDEX/SEQUENCE used a name that already exists in that schema.
Meaning
Migrations run twice, migration history out of sync with the real schema, or index names colliding (index names are unique per schema, not per table).
Common causes
- Migration re-run or history table out of sync
- Same index name used on two tables
- Restoring into a non-empty database
⚡ Quick fix
- Use IF NOT EXISTS
- Give indexes table-specific names
- Sync migration state (e.g. mark as applied) carefully
Detailed fix by platform
PostgreSQL
CREATE INDEX IF NOT EXISTS orders_user_id_idx ON orders (user_id);
How to diagnose
- Object — Table, index or sequence?
- Migrations — History matches schema?
🔧 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 14 Oct 2026