How to debug logical replication error "columns are missing" if they are not

From: Thomas Kellerer <shammat(at)gmx(dot)net>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: How to debug logical replication error "columns are missing" if they are not
Date: 2020-08-25 05:32:09
Message-ID: 6d2d142f-58b4-d2db-b271-700182b68b55@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 later then 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 are identical 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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Thomas Kellerer 2020-08-25 05:51:50 Re: How to debug logical replication error "columns are missing" if they are not
Previous Message Stephen Frost 2020-08-24 23:16:21 Re: Odd pg dump error: cache lookup failure