Re: [PoC] pg_upgrade: allow to upgrade publisher node
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>,
Dilip Kumar <dilipbalaut@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Bruce Momjian <bruce@momjian.us>, Julien Rouhaud <rjuju123@gmail.com>, vignesh C <vignesh21@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>
Date: 2023-09-28T09:02:01Z
Lists: pgsql-hackers
On Thu, Sep 28, 2023 at 2:22 PM Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote: > > On Fri, Sep 22, 2023 at 9:40 AM Michael Paquier <michael@paquier.xyz> wrote: > > > > On Thu, Sep 21, 2023 at 01:50:28PM +0530, Amit Kapila wrote: > > > We have discussed this point. Normally, we don't have such options in > > > upgrade, so we were hesitent to add a new one for this but there is a > > > discussion to add an --exclude-logical-slots option. We are planning > > > to add that as a separate patch after getting some more consensus on > > > it. Right now, the idea is to get the main patch ready. > > > > Okay. I am wondering if the subscriber part is OK now without an > > option, but that could also be considered separately, as well. At > > least I hope so. > > +1 for an option to skip upgrade logical replication slots for the > following reasons: > - one may not want the logical replication slots on the upgraded > instance immediately - unless the upgraded instance is tested and > determined to be performant. > - one may not want the logical replication slots on the upgraded > instance immediately - no logical replication setup is wanted on the > new instance perhaps because of an architectural/organizational > decision. > - one may take backup of the postgres instance with logical > replication slots using any of the file system/snapshot based backup > mechanisms (not pg_basebackup), essentially getting the on-disk > replication slots data as well; the pg_upgrade may fail on the > backed-up instance. > > I agree to have it as a 0002 patch once the design and things are > finalized for the main patch. > Thanks for understanding that it can be done as a 0002 patch because we don't have an agreement on this. Jonathan feels exactly the opposite for having an option that by default doesn't migrate slots as users always need to use the option and they may want to have slots migrated by default. So, we may consider to have an --exclude-* option. -- With Regards, Amit Kapila.
Commits
-
Fix issues in binary_upgrade_logical_slot_has_caught_up().
- 0bf62460bb9e 17.0 landed
-
Fix a random failure in 003_logical_slots.pl.
- 63c5df126abb 17.0 landed
-
Fix a test in 003_logical_slots.
- 3e36e48d8efe 17.0 landed
-
Fix uninitialized slot array access during the upgrade.
- a7db71ed2787 17.0 landed
-
Fix the test 003_logical_slots.
- 8af917be6bad 17.0 landed
-
Commit b195e6d482 forgot to update meson.build.
- 8949b978ff49 17.0 landed
-
Use shorter file names in the upgrade logical slots test.
- b195e6d482b8 17.0 landed
-
Migrate logical slots to the new node during an upgrade.
- 29d0a77fa660 17.0 landed
-
Flush logical slots to disk during a shutdown checkpoint if required.
- e0b2eed047df 17.0 landed
-
Prevent possibility of panics during shutdown checkpoint.
- c6c333436491 10.0 cited