Practise the standard verbs for tuning Postgres indexes correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ an index on the query's actual filter columns, rather than guessing which one might help without actually checking the plan.'
We 'build an index' — the standard, simple collocation for creating a Postgres index for a query. The other options are less idiomatic here.
2 / 5
Fill in: 'An unused index on a write-heavy table can ___ every insert slower than it actually needs to be.'
We say a redundant index will 'leave' inserts slower — the standard, natural collocation for the resulting overhead. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the query plan with EXPLAIN ANALYZE first, rather than adding an index nobody's actually confirmed is needed.'
We 'inspect a plan' — the standard, simple collocation for examining query execution before tuning. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every new index against real production load, rather than trusting a benchmark nobody's actually run at scale.'
We 'test an index' — the standard, simple collocation for validating index impact under real load. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ unused indexes periodically via pg_stat_user_indexes, rather than letting dead weight bloat every write forever.'
We 'remove indexes' — the standard, simple collocation for dropping unused indexes found through stats. The other options aren't idiomatic here.