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

Поиск
Список
Период
Сортировка
От Bing Xu
Тема RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Дата
Msg-id PH0PR08MB77485500E5E221D834A2F5EFB9202@PH0PR08MB7748.namprd08.prod.outlook.com
обсуждение исходный текст
Ответ на Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Список pgsql-bugs

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.g.johnston@gmail.com>
Sent: Wednesday, October 9, 2024 9:30 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 Wednesday, October 9, 2024, Bing Xu <bing.xu.uh@fujifilm.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. 

В списке pgsql-bugs по дате отправления: