RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17

Hello

Dear David

>You will,need to uninstall that extension from all of your databases before you can upgrade to a version that does not include it.
I uninstalled adminpack from the database and was able to upgrade to PostgreSQL 17 normally,
but why is there no record in the PostgreSQL 17 upgrade manual?

https://www.postgresql.org/docs/current/pgupgrade.html

best regards xu

From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Friday, September 27, 2024 10:47 PM
To: Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com>; pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17

On Thursday, September 26, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org<mailto:noreply(at)postgresql(dot)org>> wrote:
The following bug has been logged on the website:

Bug reference: 18635
Logged by: xu bing
Email address: bing(dot)xu(dot)uh(at)fujifilm(dot)com<mailto:bing(dot)xu(dot)uh(at)fujifilm(dot)com>
PostgreSQL version: 17.0
Operating system: windows server 2019 Datacenter
Description:

■Additional infos
I saw that Release Notes said that adminpack contrib extension has been
Removed, but why is it still used in pg_upgrade of PostgreSQL17.
Also please tell me the solution.

-------------------------------------
●Remove adminpack contrib extension (Daniel Gustafsson) §
　This was used by now end-of-life pgAdmin III.

https://www.postgresql.org/docs/release/17.0/
----------------------------------------------------

You will,need to uninstall that extension from all of your databases before you can upgrade to a version that does not include it.

David J.