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

Dear David
>That oversight has been corrected for v17.1

When upgrading from a version prior to PostgreSQL 17 to PostgreSQL 17,
it is necessary to uninstall adminpack.
You mentioned this has been corrected for v17.1.
but after verifying,
the same issue still exists,
and I did not find any related notes or other information in the pgupgrade notes.

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

XU BING

From: David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Wednesday, October 9, 2024 9:30 PM
To: Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com>
Cc: 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 Wednesday, October 9, 2024, Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com<mailto:bing(dot)xu(dot)uh(at)fujifilm(dot)com>> wrote:
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?

That oversight has been corrected for v17.1

David J.