Postgres Partitioning Strategy Language Collocations
Practise the standard verbs for planning Postgres table partitioning.
0 / 5 completed
1 / 5
Fill in: 'We ___ a large events table by month so old partitions can be dropped cheaply instead of deleted row by row.'
We 'partition a table' — the standard, established Postgres collocation for dividing a table by a chosen key. The other options aren't the recognised term here.
2 / 5
Fill in: 'Choosing the wrong partition key can ___ every query scanning across all partitions instead of just one.'
We say a bad key will 'force' full scans — the standard collocation for the resulting inefficiency. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a new partition automatically before the current month runs out so inserts never fail with no target partition.'
We 'create a partition' — the standard, simple collocation for provisioning a new table segment. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ query plans on partitioned tables to confirm partition pruning is actually excluding irrelevant partitions.'
We 'check plans' — the standard, simple collocation for inspecting a query execution plan. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ old partitions to cold storage after a retention period instead of leaving cold data on expensive primary disks.'
We 'move' data — the standard, simple collocation for relocating a partition to another storage tier. The other options are less idiomatic here.