On Wed, Dec 1, 2021 at 5:56 PM Marcos Pegoraro wrote:
>
>> I have an issue with logical replication after Postgresql upgrade from
>> 13 to 14 (upgraded subscriber only using pg_upgrade_cluster -m link 13
>> main). After upgrade all subscriptions were disabled so I have enabled
>> them and replicat
I think there are some bugs in Posgresql logical replication upgrade.
Because dropping and recreating subscriptions with manual
synchronization has solved the problem for me. But it is not the
correct way, IMHO.
Sergey Belyashov
ср, 1 дек. 2021 г. в 15:26, Marcos Pegoraro :
>
>
>> I have an issue
> I have an issue with logical replication after Postgresql upgrade from
> 13 to 14 (upgraded subscriber only using pg_upgrade_cluster -m link 13
> main). After upgrade all subscriptions were disabled so I have enabled
> them and replication workers successfully started.
> pg_stat_subscription cont
My table has a primary key. In addition, this is an initial load issue where
the replication identity should not matter.
-Original Message-
From: Michael Lewis
To: Donzell White
Cc: pgsql-general
Sent: Tue, Jun 30, 2020 1:05 pm
Subject: Re: Logical Replication Issue
Per the release
Per the release notes, there are some enhancements to logical replication
that came after 11.5 like 11.8 particularly related to replication identity
full. Do you have a primary key or unique index that is being used for the
replication identity?
