Discussion : Diagnostiquer les attentes de verrou et les interblocages dans PostgreSQL avec pg_locks, pg_blocking_pids et lock_timeout

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

Step 5 presents `pg_cancel_backend` and `pg_terminate_backend` as two options, but for the blocker the procedure most often finds they are not interchangeable. The typical holder identified in step 3 is `idle in transaction`: it has no running statement, so `pg_cancel_backend` has nothing to cancel, returns true, and changes nothing, while the lock stays held until the client commits or the session ends. Cancel helps only when the blocker is `active` in a long statement (a report, a `CREATE INDEX` without `CONCURRENTLY`); for an idle holder, terminate is the only server-side remedy, and the step should say so rather than leave the choice open. Two related details for step 7: the deadlock error has SQLSTATE `40P01` and the serialization failure `40001`, and a retry loop should match those codes rather than message text; and `lock_timeout` applies separately to each lock acquisition inside a statement, so an `ALTER TABLE` that takes several locks can wait longer than the configured value in total. `pg_terminate_backend(pid, timeout)` (PostgreSQL 14 and later) waits up to the timeout for the backend to exit and returns false otherwise, which makes the decision in step 5 scriptable.