| From: | Hüseyin Demir <huseyin(dot)d3r(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Report changes discarded for relations not in the subscription |
| Date: | 2026-09-09 05:00:17 |
| Message-ID: | CAB5wL7YndStOFNAW2GV2bNZOG43jZ_rOjNV_+KTTRL8p3bH7RA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hayato,
The source version is 14 and the target is 18.
Hayato Kuroda (Fujitsu) <kuroda(dot)hayato(at)fujitsu(dot)com>, 9 Eyl 2026 Çar,
05:57 tarihinde şunu yazdı:
>
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-09-09 05:05:10 | Re: Follow-up review items for update_deleted |
| Previous Message | Amit Kapila | 2026-09-09 04:59:16 | Re: Remove stale XXX comment in logical launcher |