Request a Demo
Home   >   mailing lists

RE: [PATCH] Preserve replication origin OIDs in pg_upgrade - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: [PATCH] Preserve replication origin OIDs in pg_upgrade
Date
Msg-id TYRPR01MB12156B9573547DC15C6609619F53C2@TYRPR01MB12156.jpnprd01.prod.outlook.com
Whole thread
In response to Re: [PATCH] Preserve replication origin OIDs in pg_upgrade  (Ajin Cherian <itsajin@gmail.com>)
List pgsql-hackers
Tree view 
Dear Ajin,

Thanks for updating the patch. Let me share my two high-level comments.

1.
Can you clarify the policy for backward compatibility? In other words, should we
preserve subscription OIDs and migrate replication origins from PG19- instances?
Similar commits 9a17be1 and 29d0a77 did not allow migrating objects from released
versions.

2.
I found that other objects use global variables like binary_upgrade_next_xxx to
specify the next OID. Can we follow the manner even for replication origins?
Or it's not a good approach because of some reasons?

BTW, cfbot got angry with your patch.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

pgsql-hackers by date:

Previous
From: SATYANARAYANA NARLAPURAM
Date:
Subject: Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block
Next
From: Alexander Korotkov
Date:
Subject: Re: Fix bug with accessing to temporary tables of other sessions