Practise the standard verbs for diagnosing and preventing Postgres deadlocks.
0 / 5 completed
1 / 5
Fill in: 'We ___ the deadlock error log closely to see exactly which two transactions were fighting over the same rows.'
We 'inspect' a log — the standard, established debugging collocation for examining error details. The other options aren't the recognised term here.
2 / 5
Fill in: 'Two transactions locking the same rows in opposite order can ___ a deadlock that Postgres has to break itself.'
We say conflicting lock order will 'create' a deadlock — the standard, simple collocation for the resulting condition. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a consistent lock ordering across all code paths so two transactions never wait on each other in a cycle.'
We 'enforce' ordering — the standard, established collocation for requiring a consistent access pattern. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ retry logic around deadlock-prone transactions since Postgres automatically aborts one side of a deadlock.'
We 'add logic' — the standard, simple collocation for including a piece of handling code. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ deadlock frequency in monitoring so a sudden spike after a deploy gets noticed quickly.'
We 'track' frequency — the standard collocation for monitoring how often an event occurs. The other options aren't idiomatic here.