How to debug logical replication error "columns are missing" if they are not
От | Thomas Kellerer |
---|---|
Тема | How to debug logical replication error "columns are missing" if they are not |
Дата | |
Msg-id | 6d2d142f-58b4-d2db-b271-700182b68b55@gmx.net обсуждение исходный текст |
Ответы |
Re: How to debug logical replication error "columns are missing" if they are not
Re: How to debug logical replication error "columns are missing" if they are not |
Список | pgsql-admin |
Hello, we have a a logical replication from Postgres 11 to Postgres 12. We did some structural changes to the published tables. The changes to the subscriber where applied about 60 minutes laterthen those on the publisher. Obviously before the subscriber's tables where synced the replication failed. But even though the tables are now completely identical, the subscriber still claims: logical replication target relation "public.employee" is missing some replicated columns I double checked multiple times that the tables are now identical by doing a diff of the "pg_dump -s" outputs - they areidentical in the CREATE TABLE part. The table is listed with state "r" (ready) in pg_subscription_rel How can I find out which columns it thinks are missing? And how do I convince the subscriber that the tables *are* identical? Thanks in advance Thomas
В списке pgsql-admin по дате отправления: