hard20 pts · first answer countsreplicationpostgresql

Logical replication stopped after a migration

You use logical replication to upgrade from PostgreSQL 13 to 17. A developer adds a column on the publisher, and the subscriber starts failing. Why?

A.Logical replication only supports tables without primary keysB.The subscriber must be the same major versionC.Logical replication does not replicate DDL, so the subscriber lacks the new column; apply schema changes on the subscriber firstD.Adding columns always requires a full resync of all tables

← Index-only scan still reads the table pg_upgrade --link and rollback →