Dear Hüseyin, > I encountered an issue after a pg_upgrade of a subscriber instance. > pg_subscription_rel came back empty, and the apply worker then discarded > every incoming change while the replication origin and the publisher > slot's confirmed_flush_lsn advanced past the discarded rows. Both ends > durably recording the transactions as applied, with nothing in either log > to say otherwise.
To confirm, what was the datasabse version of old and new cluster? 9a17be1e2 allowed to migrate the content of pg_subscription_rel catalog[1]. It means it's unexpected behavior and must be fixed if old one is PG17+. [1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9a17be1e2 Best regards, Hayato Kuroda FUJITSU LIMITED
