PostgreSQL Error Reference

Every error, explained

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

578 errors documentedFree diagnostics on every pageAll PG versions covered

Showing 456 of 578 errors

53100 ERROR

could not extend file “…”: No space left on device — 53100

disk_full

PostgreSQL error "could not extend file "…": No space left on device" (SQLSTATE 53100): what it means, common causes, and how to fix it.

Insufficient Resources
53100 ERROR

could not write to file “…”: No space left on device — 53100

disk_full

PostgreSQL error "could not write to file "…": No space left on device" (SQLSTATE 53100): what it means, common causes, and how to fix it.

Insufficient Resources
53100 ERROR

could not write to file “…”: No space left on device — 53100

disk_full

PostgreSQL error "could not write to file …: No space left on device — 53100" (SQLSTATE 53100): what it means, common causes, and how to fix it.

Insufficient Resources
53100 ERROR

Disk Full — SQLSTATE 53100

disk_full

The server could not write because the disk or tablespace is full.

Insufficient Resources
53200 ERROR

out of memory — 53200

out_of_memory

PostgreSQL error "out of memory" (SQLSTATE 53200): what it means, common causes, and how to fix it.

Insufficient Resources
53200 ERROR

Out Of Memory — SQLSTATE 53200

out_of_memory

The server could not allocate memory for the operation.

Insufficient Resources
53200 FATAL

could not create shared memory segment — 53200

out_of_memory

PostgreSQL error "could not create shared memory segment — 53200" (SQLSTATE 53200): what it means, common causes, and how to fix it.

Insufficient Resources
53200 FATAL

could not create semaphores: No space left on device — 53200

out_of_memory

PostgreSQL error "could not create semaphores: No space left on device — 53200" (SQLSTATE 53200): what it means, common causes, and how to fix it.

Insufficient Resources
53200 ERROR

out of memory — 53200

out_of_memory

PostgreSQL error "out of memory — 53200" (SQLSTATE 53200): what it means, common causes, and how to fix it.

Insufficient Resources
53300 FATAL

too many connections for role “…” — 53300

too_many_connections

PostgreSQL error "too many connections for role "…"" (SQLSTATE 53300): what it means, common causes, and how to fix it.

Insufficient Resources
53300 FATAL

remaining connection slots are reserved for non-replication superuser connections — 53300

too_many_connections

PostgreSQL error "remaining connection slots are reserved for non-replication superuser connections" (SQLSTATE 53300): what it means, common causes, and...

Insufficient Resources
53300 FATAL

sorry, too many clients already — 53300

too_many_connections

PostgreSQL error "sorry, too many clients already" (SQLSTATE 53300): what it means, common causes, and how to fix it.

Insufficient Resources
53300 ERROR

Too Many Connections — SQLSTATE 53300

too_many_connections

The server reached its connection limit and rejected the new connection.

Insufficient Resources
53300 FATAL

too many connections for role “…” — 53300

too_many_connections

PostgreSQL error "too many connections for role … — 53300" (SQLSTATE 53300): what it means, common causes, and how to fix it.

Insufficient Resources
53300 FATAL

too many connections for database “…” — 53300

too_many_connections

PostgreSQL error "too many connections for database "…"" (SQLSTATE 53300): what it means, common causes, and how to fix it.

Insufficient Resources
53400 ERROR

temporary file size exceeds temp_file_limit (N kB) — 53400

configuration_limit_exceeded

PostgreSQL error "temporary file size exceeds temp_file_limit (N kB)" (SQLSTATE 53400): what it means, common causes, and how to fix it.

Insufficient Resources
53400 ERROR

Configuration Limit Exceeded — SQLSTATE 53400

configuration_limit_exceeded

A configured resource limit was exceeded.

Insufficient Resources
53400 ERROR

maximum number of prepared transactions reached — 53400

configuration_limit_exceeded

PostgreSQL error "maximum number of prepared transactions reached — 53400" (SQLSTATE 53400): what it means, common causes, and how to fix it.

Insufficient Resources
54000 ERROR

row is too big: size N, maximum size N — 54000

program_limit_exceeded

PostgreSQL error "row is too big: size N, maximum size N" (SQLSTATE 54000): what it means, common causes, and how to fix it.

Program Limit Exceeded
54000 ERROR

index row size N exceeds maximum N for index “…” — 54000

program_limit_exceeded

PostgreSQL error "index row size N exceeds maximum N for index "…"" (SQLSTATE 54000): what it means, common causes, and how to fix it.

Program Limit Exceeded
54000 ERROR

Program Limit Exceeded — SQLSTATE 54000

program_limit_exceeded

A hard internal program limit was exceeded.

Program Limit Exceeded
54000 ERROR

index row size N exceeds maximum N for index “…” — 54000

program_limit_exceeded

PostgreSQL error "index row size N exceeds maximum N for index … — 54000" (SQLSTATE 54000): what it means, common causes, and how to fix it.

Program Limit Exceeded
54000 ERROR

target lists can have at most N entries — 54000

program_limit_exceeded

PostgreSQL error "target lists can have at most N entries" (SQLSTATE 54000): what it means, common causes, and how to fix it.

Program Limit Exceeded
54001 ERROR

stack depth limit exceeded — 54001

statement_too_complex

PostgreSQL error "stack depth limit exceeded" (SQLSTATE 54001): what it means, common causes, and how to fix it.

Program Limit Exceeded