From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: How to debug logical replication error "columns are missing" if they are not
Date: Tue, 25 Aug 2020 07:51:50 +0200
Message-ID: <86ce53d9-5b46-d652-78d4-2bdac368a6b0@gmx.net> (raw)
In-Reply-To: <6d2d142f-58b4-d2db-b271-700182b68b55@gmx.net>
References: <6d2d142f-58b4-d2db-b271-700182b68b55@gmx.net>
Thomas Kellerer schrieb am 25.08.2020 um 07:32:
> 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?
This is getting stranger:
I dropped the table from the publication.
After refreshing the subscription the error is still shown in the logfile even though that table shouldn't be replicated any more.
Is it possible that the error message mentions an unrelated table?
How can I find out which table really causes the problem?
Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: How to debug logical replication error "columns are missing" if they are not
In-Reply-To: <86ce53d9-5b46-d652-78d4-2bdac368a6b0@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox