Horton

Re: A recent message added to pg_upgade

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: vignesh C <vignesh21@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>, Tom Lane <tgl@sss.pgh.pa.us>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, smithpb2250@gmail.com, bharath.rupireddyforpostgres@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2025-07-11T03:38:38Z
Lists: pgsql-hackers 
On Fri, Jul 11, 2025 at 8:03 AM vignesh C <vignesh21@gmail.com> wrote:
>
> On Thu, 10 Jul 2025 at 11:47, Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > >
> > PFA, patch for v17.
>
> Thanks for working on this, I don't have any more comments.
>

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.

[1] - https://www.postgresql.org/message-id/1625598.1752180243%40sss.pgh.pa.us

-- 
With Regards,
Amit Kapila.

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.