| From: | Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Ajin Cherian <itsajin(at)gmail(dot)com> |
| Cc: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Preserve replication origin OIDs in pg_upgrade |
| Date: | 2026-07-21 11:28:14 |
| Message-ID: | CANhcyEV0OPEPo8JJC-JbF8R0ohtC-UQn9-WOqaCX1MAhUu=uhw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> With this patch, I observed that replication origins whose remote_lsn
> is '0/00000000' are not present on the upgraded node when
> max_logical_replication_workers is set to 0.
> Is this behaviour expected?
Small clarification: I meant that the replication origins whose
remote_lsn was 0/00000000 before the upgrade are not present in
pg_replication_origin_status on the upgraded node. The replication
origin entries themselves still exist in pg_replication_origin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2026-07-21 11:37:07 | RE: sequencesync worker race with REFRESH SEQUENCES |
| Previous Message | Nazir Bilal Yavuz | 2026-07-21 11:26:35 | Re: ci: namespace ccache by PostgreSQL major version |