PostgreSQL Error Reference

Every error, explained

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

3908 errors documentedFree diagnostics on every pageAll PG versions covered

Showing 3720 of 3908 errors

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
57P01 FATAL

terminating connection due to administrator command — 57P01

admin_shutdown

PostgreSQL error "terminating connection due to administrator command — 57P01" (SQLSTATE 57P01): what it means, common causes, and how to fix it.

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
57P03 FATAL

the database system is not yet accepting connections — 57P03

cannot_connect_now

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

Operator Intervention
57P03 ERROR

Cannot Connect Now — SQLSTATE 57P03

cannot_connect_now

The server is not yet ready to accept connections.

Operator Intervention
57P03 FATAL

the database system is starting up — 57P03

cannot_connect_now

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

Operator Intervention
57P03 WARNING

requested checkpoint not completed because recovery is still in progress — 57P03

cannot_connect_now

PostgreSQL error "requested checkpoint not completed because recovery is still in progress — 57P03" (SQLSTATE 57P03): what it means, common causes, and how to fix it.

Operator Intervention
57P04 ERROR

Database Dropped — SQLSTATE 57P04

database_dropped

The connected database was dropped.

Operator Intervention
57P05 ERROR

Idle Session Timeout — SQLSTATE 57P05

idle_session_timeout

The session was closed after exceeding idle_session_timeout.

Operator Intervention
57P05 FATAL

terminating connection due to idle-session timeout — 57P05

idle_session_timeout

PostgreSQL error "terminating connection due to idle-session timeout — 57P05" (SQLSTATE 57P05): what it means, common causes, and how to fix it.

Operator Intervention
58000 ERROR

failed to send signal to postmaster: the OS error — 58000

system_error

PostgreSQL error "failed to send signal to postmaster: the OS error" (SQLSTATE 58000, system_error): what it means, common causes, and how to fix it.

System Error (errors external to PostgreSQL itself)
58000 ERROR

System Error — SQLSTATE 58000

system_error

SQLSTATE 58000 (system_error): An operating-system level error occurred (I/O or missing file).

System Error
58000 ERROR

strxfrm(), in locale “…”, writes past the specified array length — 58000

system_error

PostgreSQL error "strxfrm(), in locale "…", writes past the specified array length" (SQLSTATE 58000, system_error): what it means, common causes, and how to fix it.

System Error (errors external to PostgreSQL itself)
58000 WARNING

archive command failed with exit code N — 58000

system_error

PostgreSQL error "archive command failed with exit code N — 58000" (SQLSTATE 58000): what it means, common causes, and how to fix it.

System Error
58030 ERROR

Io Error — SQLSTATE 58030

io_error

An operating-system I/O error occurred.

System Error
58030 ERROR

could not read block N in file “…”: read only 0 of N bytes — 58030

io_error

PostgreSQL error "could not read block N in file "…": read only 0 of N bytes" (SQLSTATE 58030): what it means, common causes, and how to fix it.

System Error