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

From: Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Date: 2024-11-20 03:31:15
Message-ID: PH0PR08MB7748E3F1A4BEC6887B0B494CB9212@PH0PR08MB7748.namprd08.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(dot)g(dot)johnston(at)gmail(dot)com>
Sent: Tuesday, November 19, 2024 10:10 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 Mon, Nov 18, 2024 at 11:23 PM Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com<mailto:bing(dot)xu(dot)uh(at)fujifilm(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nathan Bossart 2024-11-20 03:47:09 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Previous Message Michael Paquier 2024-11-20 00:41:58 Re: pg_rewind WAL segments deletion pitfall