| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'shveta malik' <shveta(dot)malik(at)gmail(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com> |
| Cc: | Rui Zhao <zhaorui126(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(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-08-27 06:14:31 |
| Message-ID: | OS9PR01MB1214938016C2B8568B73DC761F5AD2@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Shveta,
> a) Check for pre-existing origins on the new cluster regardless of the
> old cluster's origin count?
> b) Or update the doc to make it consistent with code, at-least for our
> origin case?
> c) Leave things as they are?
Personally I prefer c), no need to update documents and codes, because it's the
same behavior for replication slots.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahendra Singh Thalor | 2026-08-27 06:22:53 | Re: Non-text mode for pg_dumpall |
| Previous Message | Ewan Young | 2026-08-27 05:57:59 | Use pg_neg_s*_overflow() for open-coded negation overflow checks |