Re: Invalid operation order while producing DB dump

As a workaround I have removed REPLICA IDENTITY from table closed_sessions, do cluster upgrade, and then add REPLICA IDENTITY back. Sergey Belyashov чт, 10 февр. 2022 г. в 15:09, Sergey Belyashov : > > Hi, > I have tried to upgrade my cluster from version 13 to 14 using the

Invalid operation order while producing DB dump

ates invalid order of SQL commands causing it to create a replica identity index for partition tables without connected partitions. Also it is possible that there is an error in the very strict checking for invalid index. Sergey Belyashov

Upgrade 13 to 14 with replication of partitioned table

ed", "id"); ALTER TABLE ONLY "public"."closed_sessions" REPLICA IDENTITY USING INDEX "closed_sessions_closed_id_idx"; --- closed_sessions is partitioned table and column closed is used for replica identity index. Cluster version 13 works fine... How can I upgrade the cluster? Sergey Belyashov.

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

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 : > > >&g

Logical replication issue after Postgresql upgrade from 13 to 14

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? Sergey Belyashov