PostgreSQL Error Reference

Every error, explained

SQLSTATE codes, condition names, root causes, diagnostic queries, and recovery steps — structured for engineers running PostgreSQL in production.

3779 errors documentedFree diagnostics on every pageAll PG versions covered

Showing 3600 of 3779 errors

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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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

57 — Operator Intervention
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

57 — Operator Intervention
57P01 FATAL

Admin Shutdown — SQLSTATE 57P01

admin_shutdown

The connection was terminated by an administrator command or server shutdown.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
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.

Operator Intervention
57P01 FATAL

postmaster exited during data checksum processing in “…” — 57P01

admin_shutdown

PostgreSQL error "postmaster exited during data checksum processing in "…"" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.

Operator Intervention
57P01 FATAL

postmaster exited during data checksums processing — 57P01

admin_shutdown

PostgreSQL error "postmaster exited during data checksums processing" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.

Operator Intervention
57P01 FATAL

postmaster exited during REPACK command — 57P01

admin_shutdown

PostgreSQL error "postmaster exited during REPACK command" (SQLSTATE 57P01, admin_shutdown): what it means, common causes, and how to fix it.

Operator Intervention
57P01 FATAL

SQLSTATE 57P01 — admin_shutdown: FATAL terminating connection due to administrator command

admin_shutdown

Application users receive FATAL: terminating connection due to administrator command. This happens because a DBA ran pg_terminate_backend() or SELECT pg_terminate_backend(pid) FROM pg_stat_activity WH

57 — Operator Intervention
57P02 PANIC

Crash Shutdown — SQLSTATE 57P02

crash_shutdown

SQLSTATE 57P02 (crash_shutdown): The statement or session was canceled or terminated by timeout, admin, or shutdown.

Operator Intervention
57P02 FATAL

terminating connection because of crash of another server process — 57P02

crash_shutdown

PostgreSQL error "terminating connection because of crash of another server process" (SQLSTATE 57P02): what it means, common causes, and how to fix it.

Operator Intervention
57P03 FATAL

the database system is not accepting connections — 57P03

cannot_connect_now

PostgreSQL error "the database system is not accepting connections" (SQLSTATE 57P03, cannot_connect_now): what it means, common causes, and how to fix it.

Operator Intervention
57P03 FATAL

the database system is starting up — 57P03

cannot_connect_now

PostgreSQL error "the database system is starting up" (SQLSTATE 57P03): what it means, common causes, and how to fix it.

Operator Intervention
57P03 FATAL

the database system is shutting down — 57P03

cannot_connect_now

PostgreSQL error "the database system is shutting down" (SQLSTATE 57P03): what it means, common causes, and how to fix it.

Operator Intervention
57P03 FATAL

the database system is in recovery mode — 57P03

cannot_connect_now

PostgreSQL error "the database system is in recovery mode" (SQLSTATE 57P03): what it means, common causes, and how to fix it.

Operator Intervention