Every error, explained
SQLSTATE codes, condition names, root causes, diagnostic queries, and recovery steps — structured for engineers running PostgreSQL in production.
Showing 408 of 578 errors
42P01
ERROR
logical replication target relation “….” does not exist — 42P01
undefined_table
PostgreSQL error "logical replication target relation "…." does not exist — 42P01" (SQLSTATE 42P01): what it means, common causes, and how to fix it.
42P01
ERROR
missing FROM-clause entry for table “…” — 42P01
undefined_table
PostgreSQL error "missing FROM-clause entry for table "…"" (SQLSTATE 42P01): what it means, common causes, and how to fix it.
42P01
ERROR
relation “…” does not exist — 42P01
undefined_table
PostgreSQL error "relation "…" does not exist" (SQLSTATE 42P01): what it means, common causes, and how to fix it.
42P01
ERROR
Undefined Table — SQLSTATE 42P01
undefined_table
The table or view does not exist, or is not visible on the search_path.
42P02
ERROR
Undefined Parameter — SQLSTATE 42P02
undefined_parameter
SQLSTATE 42P02 (undefined_parameter): The SQL is malformed or references a missing object or privilege.
42P02
ERROR
there is no parameter $N — 42P02
undefined_parameter
PostgreSQL error "there is no parameter $N" (SQLSTATE 42P02): what it means, common causes, and how to fix it.
42P03
ERROR
cursor “…” already exists — 42P03
duplicate_cursor
PostgreSQL error "cursor "…" already exists" (SQLSTATE 42P03): what it means, common causes, and how to fix it.
42P03
ERROR
Duplicate Cursor — SQLSTATE 42P03
duplicate_cursor
SQLSTATE 42P03 (duplicate_cursor): The SQL is malformed or references a missing object or privilege.
42P04
ERROR
database “…” already exists — 42P04
duplicate_database
PostgreSQL error "database "…" already exists" (SQLSTATE 42P04): what it means, common causes, and how to fix it.
42P04
ERROR
Duplicate Database — SQLSTATE 42P04
duplicate_database
A database with that name already exists.
42P05
ERROR
Duplicate Prepared Statement — SQLSTATE 42P05
duplicate_prepared_statement
SQLSTATE 42P05 (duplicate_prepared_statement): The SQL is malformed or references a missing object or privilege.
42P05
ERROR
prepared statement “…” already exists — 42P05
duplicate_prepared_statement
PostgreSQL error "prepared statement "…" already exists" (SQLSTATE 42P05): what it means, common causes, and how to fix it.
42P06
ERROR
schema “…” already exists — 42P06
duplicate_schema
PostgreSQL error "schema "…" already exists" (SQLSTATE 42P06): what it means, common causes, and how to fix it.
42P06
ERROR
Duplicate Schema — SQLSTATE 42P06
duplicate_schema
A schema with that name already exists.
42P07
ERROR
relation “…” already exists — 42P07
duplicate_table
PostgreSQL error "relation "…" already exists" (SQLSTATE 42P07): what it means, common causes, and how to fix it.
42P07
ERROR
Duplicate Table — SQLSTATE 42P07
duplicate_table
A relation with that name already exists.
42P07
ERROR
relation “…” already exists — 42P07
duplicate_table
PostgreSQL error "relation … already exists — 42P07" (SQLSTATE 42P07): what it means, common causes, and how to fix it.
42P08
ERROR
Ambiguous Parameter — SQLSTATE 42P08
ambiguous_parameter
SQLSTATE 42P08 (ambiguous_parameter): The SQL is malformed or references a missing object or privilege.
42P09
ERROR
Ambiguous Alias — SQLSTATE 42P09
ambiguous_alias
SQLSTATE 42P09 (ambiguous_alias): The SQL is malformed or references a missing object or privilege.
42P10
ERROR
cannot use column reference in DEFAULT expression — 42P10
invalid_column_reference
PostgreSQL error "cannot use column reference in DEFAULT expression" (SQLSTATE 42P10): what it means, common causes, and how to fix it.
42P10
ERROR
for SELECT DISTINCT, ORDER BY expressions must appear in select list — 42P10
invalid_column_reference
PostgreSQL error "for SELECT DISTINCT, ORDER BY expressions must appear in select list" (SQLSTATE 42P10): what it means, common causes, and how to fix it.
42P10
ERROR
GROUP BY position … is not in select list — 42P10
invalid_column_reference
PostgreSQL error "GROUP BY position … is not in select list" (SQLSTATE 42P10): what it means, common causes, and how to fix it.
42P10
ERROR
there is no unique or exclusion constraint matching the ON CONFLICT specification — 42P10
invalid_column_reference
PostgreSQL error "there is no unique or exclusion constraint matching the ON CONFLICT specification" (SQLSTATE 42P10): what it means, common causes, and...
42P10
ERROR
Invalid Column Reference — SQLSTATE 42P10
invalid_column_reference
SQLSTATE 42P10 (invalid_column_reference): The SQL is malformed or references a missing object or privilege.