Re: Logical replication issue after Postgresql upgrade from 13 to 14

From: Sergey Belyashov <sergey(dot)belyashov(at)gmail(dot)com>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Logical replication issue after Postgresql upgrade from 13 to 14
Date: 2021-12-01 12:30:55
Message-ID: CAOe0RDxfFWQxvhde+bn+SrKu_2g56y3MJpqRc_uiCYXScWyJJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <marcos(at)f10(dot)com(dot)br>:
>
>
>> 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 contains list of all subscriptions. All times in
>> this table is near current time (replication workers receives data
>> from servers). But no changes in destination table since cluster
>> upgrade (on publishers tables are changed). What I'm doing wrong and
>> how to fix issue?
>
>
> Amit, wouldn't it be better to document all steps needed to use pg_upgrade with logical replication ?
> Sergey is showing a different problem than mine.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthias Apitz 2021-12-01 12:42:07 Linux: directory change .../lib to .../lib64
Previous Message Marcos Pegoraro 2021-12-01 12:26:16 Re: Logical replication issue after Postgresql upgrade from 13 to 14