Symptoms
The connected database was dropped.
- The error is written to the server log and returned to the client carrying
SQLSTATE 57P04. - Any driver (libpq, JDBC, psycopg, npgsql, pgx) surfaces this code in its error object so you can branch on it programmatically.
- PL/pgSQL can trap it by name:
EXCEPTION WHEN database_dropped THEN.
Environment
Severity: ERROR | PostgreSQL versions: 12, 13, 14, 15, 16, 17
Commonly coincides with restarts, failover, maintenance, or network events; check server uptime and the log around the timestamp.
Root Cause
The database the session was using has been removed.
Diagnostic Queries
Recovery
Steps to resolve 57P04:
- Reconnect to a valid database.
- Ensure clients are not pinned to a database that was dropped.
Reference: PostgreSQL error codes — Class 57 (Operator Intervention).
Was this helpful?
Thanks — noted. This helps keep the database accurate.