Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Date
Msg-id CAKFQuwaSk6d5eAAhGnP7H3ZuoV8d66mV2wxcCPigG5CQijcByw@mail.gmail.com
Whole thread Raw
In response to RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17  (Bing Xu <bing.xu.uh@fujifilm.com>)
List pgsql-bugs
Tree view
On Tuesday, November 19, 2024, Bing Xu <bing.xu.uh@fujifilm.com> wrote:

Thank you for your response.

 >https://www.postgresql.org/docs/current/release-17.html#RELEASE-17-MIGRATION

Is it the following passage?


Yes
 

Instead of letting pg_upgrade.exe automatically uninstall adminpack.

Is my understanding correct?


pg_upgrade will never uninstall anything.  It installs whatever is in the source cluster unconditionally. Except catalogs, which are instead built in the new cluster during initdb.

David J.

pgsql-bugs by date:

Previous
From: Bing Xu
Date:
Subject: RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Next
From: Tom Lane
Date:
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails