Re: A recent message added to pg_upgade

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, smithpb2250(at)gmail(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: A recent message added to pg_upgade
Date: 2025-07-10 04:12:32
Message-ID: 1454511.1752120752@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-07-10 04:13:20 Re: A recent message added to pg_upgade
Previous Message Amit Kapila 2025-07-10 04:10:02 Re: A recent message added to pg_upgade