Practise the standard verbs for managing Postgres connection pools safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a connection pooler like PgBouncer in front of Postgres so short-lived app connections don't overwhelm it.'
We 'deploy' a pooler — the standard, established infrastructure collocation for putting a service into place. The other options aren't the recognised term here.
2 / 5
Fill in: 'Too many application instances opening direct connections can ___ Postgres past its max_connections limit.'
We say excess connections will 'push' Postgres past its limit — the standard, natural collocation for the resulting overload. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ pool size carefully so it's large enough for peak load but never exceeds the database's own connection limit.'
We 'size' a pool — the standard collocation for choosing an appropriate capacity value. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ idle connections after a timeout so a leaked, forgotten connection doesn't sit open forever.'
We 'close a connection' — the standard, simple collocation for terminating it deliberately. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ pool utilisation in our monitoring dashboard so a saturated pool gets caught before requests start queueing.'
We 'monitor' utilisation — the standard collocation for ongoing observation of a resource metric. The other options aren't idiomatic here.