postgres-errors-statement-timeouts

Quick Reference :

PostgreSQL has five timeout GUCs. Each one is a safety bound, and each one is 0 (disabled) by default. A production database with all five at 0 has no defense against a runaway query, a leaked transaction, or a migration that queues behind a slow SELECT.

ERROR:  canceling statement due to statement timeout      -- SQLSTATE 57014
ERROR:  canceling statement due to lock timeout           -- SQLSTATE 55P03
FATAL:  terminating connection due to idle-in-transaction timeout  -- 25P03

The five timeouts, what they bound, and what they do when hit :