Logical replication capture
Committed changes are read from the write ahead log, so after the first load only what actually changed moves into MotherDuck.
Replicate PostgreSQL into MotherDuck with Polytomic using logical replication, so your application database becomes queryable in DuckDB without analytical load ever touching it. Change capture can even run from a read replica, and ETL and reverse ETL both run on the schedule you choose.
Committed changes are read from the write ahead log, so after the first load only what actually changed moves into MotherDuck.
On PostgreSQL 16 and later, change capture can run against a read replica, keeping the extra read load off the primary serving your product.
JSON and JSONB land as queryable DuckDB values. Native PostgreSQL array columns currently normalize to JSON rather than typed DuckDB lists.

Bec Hu
Head of Sales Ops, Chowbus
“The support is among the best I have ever encountered.”
Follow these simple steps to connect MotherDuck with PostgreSQL in minutes
Connect MotherDuck
Connect PostgreSQL
Create sync
Enable sync
Connect MotherDuck to Polytomic with an access token and your database name.
Connect PostgreSQL to Polytomic with host, port, database, and credentials.
Sync data in either direction between MotherDuck and PostgreSQL. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between MotherDuck and PostgreSQL.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.