Re: A recent message added to pg_upgade

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>

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

Cc: Amit Kapila <amit.kapila16@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:13:20Z

Lists: pgsql-hackers

On Thu, Jul 10, 2025 at 9:42 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

Right..

-- 
Regards,
Dilip Kumar
Google

Commits

Fix the handling of two GUCs during upgrade.
- 72e6c08fea7c 19 (unreleased) landed
- f36e5774510d 18.0 landed
- 24f6c1bd41d0 17.6 landed
Rework how logirep launchers are stopped during pg_upgrade
- 08c3ad27eb53 17.0 landed
Prohibit max_slot_wal_keep_size to value other than -1 during upgrade.
- 8bfb231b43d7 17.0 landed
Prevent startup of logical replication launcher during pg_upgrade
- 7021d3b17664 17.0 cited
Migrate logical slots to the new node during an upgrade.
- 29d0a77fa660 17.0 cited