Estuary limits recovery backfills without filtering ongoing changes
Estuary’s PostgreSQL connector now accepts a per-table SQL filter for backfills, letting operators recover a selected range instead of rereading an entire large table. The filter affects historical reads only: ongoing change-data capture still receives new changes independently. New schema and table discovery controls, plus configurable rediscovery, let operators trade faster schema detection against additional database catalog queries.
Estuary · PostgreSQL · Oct 28, 2026
Why it matters
Recovery scope and continuous replication are separate controls, a distinction that matters when restoring data or estimating database load.
More context
The managed connector needs PostgreSQL logical replication and suitable permissions. Try an indexed identifier or timestamp filter on a test binding. Changing that filter requires another backfill; the default rediscovery interval is fifteen minutes.
Keep in mind
A mistaken filter can omit needed history and is not an access-control filter for continuous changes. The vendor gives no general performance benchmark here; service pricing was not verified.
Original read