DatriseAI-first ETL

PostgreSQL to ClickHouse Integration

AI-first ETL from PostgreSQL into ClickHouse. Governed entities, incremental sync, typed landing tables.

How Datrise loads PostgreSQL into ClickHouse

Datrise syncs PostgreSQL's tables, rows, schemas, indexes, sequences, and replication slots into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

PostgreSQL: Self-managed PostgreSQL instances.

ClickHouse: Columnar OLAP engine for fast aggregations.

How PostgreSQL entities map to ClickHouse

PostgreSQL entityClickHouse objectNotes
tableshp_postgres_tablesid PK · custom fields → JSON or Map columns
rowshp_postgres_rowsid PK · linked to hp_postgres_tables
schemashp_postgres_schemasid PK · linked to hp_postgres_tables
indexeshp_postgres_indexesid PK · linked to hp_postgres_tables

FAQ

How does Datrise handle PostgreSQL's custom fields in ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

How does the PostgreSQL to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect PostgreSQL to ClickHouse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.