Schema Changes Propagation Support

PeerDB’s Postgres connector can detect schema changes in the source tables. For Postgres, BigQuery and Snowflake destinations, it can propagate some of these changes to the corresponding destination tables as well. The way each schema change is handled is documented below:

Schema Change Type	Behaviour
Adding a new column (`ALTER TABLE ADD COLUMN ...`)	Propagated automatically once the table gets an insert/update/delete, all rows after the change will have all columns filled
Adding a new column with a default value (`ALTER TABLE ADD COLUMN ... DEFAULT ...`)	Propagated automatically once the table gets an insert/update/delete, all rows after the change will have all columns filled but existing rows will not show the DEFAULT value without a full table refresh
Dropping an existing column (`ALTER TABLE DROP COLUMN ...`)	Detected, but not propagated. All rows after the change will have NULL for the dropped columns

Resyncing a CDC Mirror Replicating partitioned tables

⌘I

Home

Quickstart

PeerDB Cloud

Setup

Queues Setup

Mirror

5-minute Tutorials

Features

Data types

Best practices

Use-cases

Benchmarks

Contributing

Metrics and Tuning

FAQs