PostgreSQL deadlocks cause API 500 errors under concurrent load

Database deadlocks cause Prefect API to timeout and return HTTP 500 errors. Occurs intermittently under load, with some deployments affected while others running the same version remain stable, suggesting workload-specific triggers.

Reduce concurrent operations that acquire locks on the same tables. Review background service scheduling to minimize overlapping database operations. Ensure transaction isolation levels are appropriate. Monitor deadlock frequency in PostgreSQL logs. Consider splitting read-heavy operations to replica databases if available.