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: 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-10T04:12:32Z
Lists: pgsql-hackers 
Amit Kapila <amit.kapila16@gmail.com> writes:
> What shall we do for exposed check_hook functions
> check_max_slot_wal_keep_size() and
> check_idle_replication_slot_timeout() in backbranch? Shall we remove
> there as well or leave them to avoid the risk of breaking any
> application?

It's impossible to believe that any extension is calling those
functions.

			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.