| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Hüseyin Demir' <huseyin(dot)d3r(at)gmail(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 03:57:48 |
| Message-ID: | OS9PR01MB1214919F7483283119433FC0AF5B02@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 | Chao Li | 2026-09-09 04:02:22 | Re: pg_stat_progress_cluster: do not default to CLUSTER |
| Previous Message | Fujii Masao | 2026-09-09 03:51:56 | Re: Fix failing assert in deferred constraint trigger |