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 CAKFQuwYoA+4MA7=8Bk8aQZdfM2MyH-XH7AAkgGO-FFNVkAMiLg@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>)
Responses RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
List pgsql-bugs
Tree view
On Mon, Nov 18, 2024 at 11:23 PM Bing Xu <bing.xu.uh@fujifilm.com> wrote:

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.


Sorry, I should have been more clear, our release notes hadn't mentioned this in 17.0 and now they do.

 

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

 


You will not find version-specific commentary in the notes for the pgupgrade application.  We have release notes for them.

David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18715: replace() function silently fails if 3rd argument is null
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #18696: Compatibility Query for Updating zlib1.dll in PostgreSQL 10.2 to Address Security Vulnerabilities