Re: [PATCH] Preserve replication origin OIDs in pg_upgrade

From: Ajin Cherian <itsajin(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(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-07-09 11:37:16
Message-ID: CAFPTHDbVLyri=pehK6dT+G+QE5Kh-Zv0XEBsvAQ4PEkgmJh5SA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you all for the comments. I have tried to address all the
comments. I am not responding to each of them here. Based on the
discussion above, I have retained the logic as mentioned by Shlok to
compare active origins against max_active_replication_origins.

Attaching v11 with all comments addressed.

regards,
Ajin Cherian
Fujitsu Australia

Attachment Content-Type Size
v11-0001-Preserve-subscription-OIDs-during-pg_upgrade.patch application/octet-stream 9.4 KB
v11-0002-Preserve-replication-origin-OIDs-during-pg_upgra.patch application/octet-stream 36.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kedar Anavardekar 2026-07-09 11:41:18 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Amit Langote 2026-07-09 11:37:04 Re: PG19 FK fast path: OOB write and missed FK checks during batched