On Wed, 29 Apr 2026 at 14:11, Hayato Kuroda (Fujitsu) <[email protected]> wrote: > > Dear Ajin, > > > Sequence of Events During Upgrade > > > > 1. pg_dumpall dumps all non-subscription replication origins from the > > old cluster with their roidents and LSN positions. > > 2. pg_dump dumps each subscription, but now records the old roident > > alongside the subscription info. > > 3. During restore, pg_dumpall's output recreates non-subscription > > origins on the new cluster with their original roidents via > > binary_upgrade_create_replication_origin(). > > To confirm, why do we have to handle separately for subscription-associated > origins? I'm thinking it's not needed if the subscription's OID is preserved > during the upgrade.
+1 to preserve the subscription OID. This should make preserving replication origin easier. > I checked the old thread to preserve it [1], but it could not be accepted > because > there are no strong motivations. But I feel this is the good reason to do so > now. Here is a rebased version of the patch. Regards, Vignesh
v1-0001-Preserve-subscription-OIDs-during-pg_upgrade.patch
Description: Binary data
