From: Thomas Kellerer <shammat@gmx.net>
Subject: How to debug logical replication error "columns are missing" if they
 are not
To: pgsql-admin@lists.postgresql.org
Message-ID: <6d2d142f-58b4-d2db-b271-700182b68b55@gmx.net>
Date: Tue, 25 Aug 2020 07:32:09 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23)
 Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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 publish=
er. Obviously before the subscriber's tables where synced the replication =
failed.

But even though the tables are now completely identical, the subscriber st=
ill 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 TAB=
LE 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 convi=
nce the subscriber that the tables *are* identical?

Thanks in advance
Thomas