Practise the standard verbs for diagnosing and fixing Postgres index bloat.
0 / 5 completed
1 / 5
Fill in: 'We ___ index bloat regularly on high-churn tables so a slowly growing index doesn't quietly outsize the table it covers.'
We 'check' bloat — the standard, simple collocation for inspecting an index's wasted space. The other options are less idiomatic here.
2 / 5
Fill in: 'Frequent updates on an indexed column without regular vacuuming can ___ an index several times larger than it needs to be.'
We say frequent updates will 'leave' an index oversized — the standard, natural collocation for the resulting bloat. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a bloated index concurrently with REINDEX CONCURRENTLY so we can reclaim space without locking out writes.'
We 'rebuild an index' — the standard, established Postgres collocation for regenerating an index from scratch. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ autovacuum thresholds tighter on high-churn tables so dead tuples get cleaned before bloat has a chance to build up.'
We 'tune' thresholds — the standard, simple collocation for adjusting a configuration parameter. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ index size against table size over time so a widening gap flags a bloat problem before it hits disk limits.'
We 'track' a ratio — the standard collocation for monitoring a metric over time. The other options aren't idiomatic here.