Every error, explained
SQLSTATE codes, condition names, root causes, diagnostic queries, and recovery steps — structured for engineers running PostgreSQL in production.
Showing 3696 of 3908 errors
55P04
ERROR
unsafe use of new value “…” of enum type … — 55P04
unsafe_new_enum_value_usage
PostgreSQL error "unsafe use of new value "…" of enum type …" (SQLSTATE 55P04, unsafe_new_enum_value_usage): what it means, common causes, and how to fix it.
55P04
ERROR
unsafe use of new value of enum type — 55P04
unsafe_new_enum_value_usage
PostgreSQL error "unsafe use of new value of enum type — 55P04" (SQLSTATE 55P04): what it means, common causes, and how to fix it.
57000
ERROR
Operator Intervention — SQLSTATE 57000
operator_intervention
SQLSTATE 57000 (operator_intervention): The statement or session was canceled or terminated by timeout, admin, or shutdown.
57014
ERROR
Query Canceled — SQLSTATE 57014
query_canceled
The statement was canceled — by a timeout or an explicit cancel.
57014
ERROR
canceling statement due to user request — 57014
query_canceled
PostgreSQL error "canceling statement due to user request" (SQLSTATE 57014): what it means, common causes, and how to fix it.
57014
ERROR
canceling statement due to statement timeout — 57014
query_canceled
PostgreSQL error "canceling statement due to statement timeout" (SQLSTATE 57014): what it means, common causes, and how to fix it.
57014
FATAL
canceling authentication due to timeout — 57014
query_canceled
PostgreSQL error "canceling authentication due to timeout" (SQLSTATE 57014, query_canceled): what it means, common causes, and how to fix it.
57014
ERROR
timed out while waiting for target LSN n/n to be replayed; current… — 57014
query_canceled
PostgreSQL error "timed out while waiting for target LSN n/n to be replayed; current standby_replay LSN n/n" (SQLSTATE 57014, query_canceled): what it means, common causes, and how to fix it.
57014
ERROR
timed out while waiting for target LSN n/n to be written; current s… — 57014
query_canceled
PostgreSQL error "timed out while waiting for target LSN n/n to be written; current standby_write LSN n/n" (SQLSTATE 57014, query_canceled): what it means, common causes, and how to fix it.
57014
ERROR
timed out while waiting for target LSN n/n to be flushed; current s… — 57014
query_canceled
PostgreSQL error "timed out while waiting for target LSN n/n to be flushed; current standby_flush LSN n/n" (SQLSTATE 57014, query_canceled): what it means, common causes, and how to fix it.
57014
ERROR
timed out while waiting for target LSN n/n to be flushed; current p… — 57014
query_canceled
PostgreSQL error "timed out while waiting for target LSN n/n to be flushed; current primary_flush LSN n/n" (SQLSTATE 57014, query_canceled): what it means, common causes, and how to fix it.
57014
ERROR
SQLSTATE 57014 — query_canceled: Autovacuum Task Canceled by Lock Conflict
query_canceled
PostgreSQL logs show frequent ERROR: canceling autovacuum task messages on a busy OLTP table. Autovacuum is being cancelled because it conflicts with user queries — specifically, long-running queries
57014
ERROR
SQLSTATE 57014 — query_canceled: Statement Timeout Exceeded
query_canceled
A nightly report query runs for 45 minutes and is cancelled with ERROR: canceling statement due to statement timeout. The global statement_timeout = 30min was set to prevent runaway OLTP queries, but
57014
ERROR
canceling statement due to conflict with recovery — 57014
query_canceled
PostgreSQL error "canceling statement due to conflict with recovery — 57014" (SQLSTATE 57014): what it means, common causes, and how to fix it.
57014
ERROR
canceling autovacuum task — 57014
query_canceled
PostgreSQL error "canceling autovacuum task — 57014" (SQLSTATE 57014): what it means, common causes, and how to fix it.
57P01
FATAL
Admin Shutdown — SQLSTATE 57P01
admin_shutdown
The connection was terminated by an administrator command or server shutdown.
57P01
FATAL
terminating connection due to unexpected postmaster exit — 57P01
admin_shutdown
PostgreSQL error "terminating connection due to unexpected postmaster exit" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
terminating background worker “…” due to administrator command — 57P01
admin_shutdown
PostgreSQL error "terminating background worker "…" due to administrator command" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
postmaster exited during a parallel transaction — 57P01
admin_shutdown
PostgreSQL error "postmaster exited during a parallel transaction" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
terminating connection due to administrator command — 57P01
admin_shutdown
PostgreSQL error "terminating connection due to administrator command" (SQLSTATE 57P01): what it means, common causes, and how to fix it.
57P01
FATAL
terminating walreceiver process due to administrator command — 57P01
admin_shutdown
PostgreSQL error "terminating walreceiver process due to administrator command" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
terminating autovacuum process due to administrator command — 57P01
admin_shutdown
PostgreSQL error "terminating autovacuum process due to administrator command" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
terminating logical replication worker due to administrator command — 57P01
admin_shutdown
PostgreSQL error "terminating logical replication worker due to administrator command" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.
57P01
FATAL
cannot enable data checksums without the postmaster process — 57P01
admin_shutdown
PostgreSQL error "cannot enable data checksums without the postmaster process" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.