Deadlocks and downtime
Every second* of every day, your Postgres database could be hunting with intent to kill. *or whatever your deadlock_timeout setting is. Deadlocks happen when multiple transactions each hold a lock that the other needs, blocking both from proceeding. When a transaction has been waiting on a lock for longer than deadlock_timeout, Postgres runs its deadlock detector. If it finds a cycle, it cancels one transaction in the cycle — freeing the others to proceed. Without this process, new transactions
