Horton

Re: A recent message added to pg_upgade

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, smithpb2250@gmail.com, bharath.rupireddyforpostgres@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2025-07-11T03:48:20Z
Lists: pgsql-hackers 
Amit Kapila <amit.kapila16@gmail.com> writes:
> Thanks for the patch and verification. It looks good to me as well.
> Shall we commit this today or wait for beta2 as per email by Tom [1]?
> We are on the borderline to see that most of the BF members have run
> with this, but as the change is straightforward, I think we can
> proceed.

Release freeze doesn't start till Saturday, so if you feel
comfortable with this change, go ahead.  Waiting till closer
to the deadline does not improve your odds...

			regards, tom lane

Commits

  1. Fix the handling of two GUCs during upgrade.

  2. Rework how logirep launchers are stopped during pg_upgrade

  3. Prohibit max_slot_wal_keep_size to value other than -1 during upgrade.

  4. Prevent startup of logical replication launcher during pg_upgrade

  5. Migrate logical slots to the new node during an upgrade.