Practise the standard verbs for diagnosing slow queries with EXPLAIN ANALYZE.
0 / 5 completed
1 / 5
Fill in: 'We ___ EXPLAIN ANALYZE on a slow query so we see the actual row counts and timings, not just the planner's estimate.'
We 'run' EXPLAIN ANALYZE — the standard, simple collocation for executing a diagnostic query plan. The other options are less idiomatic here.
2 / 5
Fill in: 'Stale table statistics can ___ the planner choosing a sequential scan when an index scan would be far cheaper.'
We say stale statistics will 'cause' a bad plan choice — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the estimated row count against the actual row count to spot exactly where the planner's estimate goes wrong.'
We 'compare' counts — the standard, simple collocation for contrasting estimated versus actual values. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a missing index once EXPLAIN shows a sequential scan on a large table inside a hot query path.'
We 'add' an index — the standard, simple collocation for creating a new index in response to a plan. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ table statistics with ANALYZE after a large bulk load so the planner's next decision reflects the new data shape.'
We 'update' statistics — the standard, established Postgres collocation for refreshing the planner's data profile. The other options aren't the recognised term here.