PostgreSQL errors
Exact PostgreSQL error codes and states, explained from the emitting component outward. Start with evidence; follow the deeper links only when the first checks support them.
Open the PostgreSQL technology indexPostgreSQL too_many_connections
PostgreSQL rejected a new session because the server has reached its usable connection limit.
PostgreSQL deadlock_detected
PostgreSQL found a cycle of sessions waiting on one another and aborted one transaction to break it.
PostgreSQL unique_violation
An INSERT or UPDATE attempted to create a value combination already protected by a unique constraint or index.
PostgreSQL foreign_key_violation
A write would leave a child row referencing a parent key that does not exist, or a parent change would orphan dependent rows.
PostgreSQL serialization_failure
A serializable or repeatable-read transaction could not complete without violating the isolation guarantee.
PostgreSQL admin_shutdown
The server terminated the client connection because PostgreSQL was stopped, restarted, promoted, or explicitly instructed to end sessions.
PostgreSQL lock_not_available
A statement configured not to wait, or constrained by lock_timeout, could not acquire its required lock.
PostgreSQL undefined_table
PostgreSQL could not resolve a referenced table, view, sequence, materialized view, or other relation in the active namespace.
PostgreSQL invalid_password
The server selected a password-based authentication rule and could not validate the supplied credentials.
PostgreSQL connection_failure
An established PostgreSQL connection failed while the client was using it, leaving the current operation interrupted or uncertain.
Follow PostgreSQL failures and fixes
One useful weekly email with new error references, tools, integration notes and production lessons. No daily noise.