Postgres Logical Replication Language Collocations
Practise the standard verbs for setting up and maintaining Postgres logical replication.
0 / 5 completed
1 / 5
Fill in: 'We ___ a publication on the source database naming the exact tables to replicate, rather than shipping the entire cluster's write-ahead log.'
We 'create a publication' — the standard, established Postgres collocation for defining which tables are exposed to logical replication. The other options aren't the recognised term here.
2 / 5
Fill in: 'Replicating a table without its primary key can ___ the subscriber unable to apply updates or deletes from the replication stream at all.'
We say a missing key will 'leave' the subscriber unable to apply changes — the standard, natural collocation for the resulting failure. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ replication lag between the publisher and subscriber closely, since a stalled subscription can silently fall further behind every minute.'
We 'monitor' lag — the standard collocation for ongoing observation of a replication metric. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a subscription from scratch after a schema change breaks it, rather than trying to patch a replication slot that's already diverged.'
We 'resync a subscription' — the standard, established collocation for rebuilding a broken logical replication subscriber. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ an unused replication slot promptly, since an abandoned slot keeps forcing the publisher to retain WAL that would otherwise be recycled.'
We 'drop a slot' — the standard, simple collocation for removing an unused replication slot. The other options are less idiomatic here.