PostgreSQL to Databricks
real-time replication
TwinCommit replicates PostgreSQL to Databricks in real time by reading the PostgreSQL transaction log and applying every committed change exactly once and in commit order. Use it to feed Databricks with live PostgreSQL data for analytics, AI and reporting, with no triggers or capture tables on the source.
PostgreSQL
log reader
commit-ordered · exactly-once
Databricks
native writer
How capture works on PostgreSQL
TwinCommit uses a logical replication slot with the built-in pgoutput plugin, so there is nothing to install on the server.
Prerequisites
- ✓wal_level = logical
- ✓REPLICATION privilege
- ✓Primary key or REPLICA IDENTITY FULL
How apply works on Databricks
Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Requirements
- ✓A SQL warehouse or all-purpose cluster
- ✓A Unity Catalog volume or external location for staging
- ✓A service principal with MODIFY on the target schema
Setup
Set up PostgreSQL → Databricks in four steps
- 1
Prepare PostgreSQL
Run twincommit check. It verifies wal_level = logical and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Databricks
Add a target block for Databricks. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: postgres
dsn: ${SOURCE_DSN}
slot: twincommit
target:
type: databricks
host: adb-1234567890.12.azuredatabricks.net
warehouse: replication-wh
catalog: main
schema: replica
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]PostgreSQL to Databricks replication FAQ
How does TwinCommit replicate PostgreSQL to Databricks?
+
TwinCommit reads changes from the PostgreSQL transaction log, buffers them per transaction, and applies each committed transaction to Databricks in commit order. Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Does PostgreSQL to Databricks replication need triggers or capture tables?
+
No. TwinCommit reads the PostgreSQL log directly and creates no objects in the source database.
Is PostgreSQL to Databricks replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Databricks transaction as the data, so a crash or restart never loses or duplicates a transaction.
What PostgreSQL versions are supported?
+
PostgreSQL 13–18 · Amazon RDS and Aurora · Azure Flexible Server · Cloud SQL · AlloyDB.
Stream PostgreSQL to Databricks today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.