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 Bing Xu
Subject RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Date
Msg-id PH0PR08MB7748E3F1A4BEC6887B0B494CB9212@PH0PR08MB7748.namprd08.prod.outlook.com
Whole thread Raw
In response to Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
List pgsql-bugs
Tree view

Dear David

 

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

 

Thank you for your response.

Could you please tell me specifically where it is documented?

 

BINGXU

 

From: David G. Johnston <david.g.johnston@gmail.com>
Sent: Tuesday, November 19, 2024 10:10 PM
To: Bing Xu <bing.xu.uh@fujifilm.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17

 

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: Erik Wienhold
Date:
Subject: Re: BUG #18715: replace() function silently fails if 3rd argument is null
Next
From: Nathan Bossart
Date:
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails