DDL replication propagates database structure changes, but inconsistent schemas can break logical replication. Renaming a column on one node leaves the other expecting the old replicated column. section 5.5
A column rename breaks replication
On beta, run `ALTER TABLE support.tickets RENAME opened_at TO logged_at;`. An insert on alpha succeeds, but beta reports that `support.tickets` is missing replicated column `opened_at`; the logical replication worker exits and restarts. section 5.5
ALTER TABLE support.tickets RENAME opened_at TO logged_at; ALTER TABLE
Inspect the schema-changing statement that creates the mismatch. section 5.5
Safe schema changes require carefully managed orchestration across nodes, balancing conflict avoidance and replication availability. Consistent DDL replication remains a major obstacle to homemade multi-master PostgreSQL clusters. section 5.5
