Postgres JSON Column Indexing Language Collocations
Practise the standard verbs for indexing jsonb columns in Postgres.
0 / 5 completed
1 / 5
Fill in: 'We ___ a GIN index on the jsonb column so containment queries against nested keys don't fall back to a full table scan.'
We 'create an index' — the standard, simple collocation for adding a new index to a table. The other options are less idiomatic here.
2 / 5
Fill in: 'Storing everything as loosely structured jsonb without any indexing can ___ even simple lookups devolving into full scans.'
We say unindexed jsonb will 'leave' lookups scanning the whole table — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a functional expression index on a frequently queried nested key instead of indexing the entire jsonb column.'
We 'add' an index — the standard, simple collocation for creating a new index in response to a query pattern. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ EXPLAIN on a jsonb containment query to confirm the planner is actually using the GIN index, not scanning every row.'
We 'run' EXPLAIN — the standard, simple collocation for executing a diagnostic query plan. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ frequently accessed fields out of jsonb into real typed columns once a schema shape has clearly stabilised.'
We 'extract' a field — the standard, established collocation for promoting a JSON key into its own column. The other options aren't the recognised term here.