Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
| От | David G. Johnston |
|---|---|
| Тема | Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 |
| Дата | |
| Msg-id | CAKFQuwap+BUzOvd==rOifJ6D5j1-1N_6qBGNfjgouoZJg8e7DQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 (PG Bug reporting form <noreply@postgresql.org>) |
| Ответы |
RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
|
| Список | pgsql-bugs |
On Thursday, September 26, 2024, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 18635
Logged by: xu bing
Email address: bing.xu.uh@fujifilm.com
PostgreSQL version: 17.0
Operating system: windows server 2019 Datacenter
Description:
■Additional infos
I saw that Release Notes said that adminpack contrib extension has been
Removed, but why is it still used in pg_upgrade of PostgreSQL17.
Also please tell me the solution.
-------------------------------------
●Remove adminpack contrib extension (Daniel Gustafsson) §
This was used by now end-of-life pgAdmin III.
https://www.postgresql.org/docs/release/17.0/
----------------------------------------------------
You will,need to uninstall that extension from all of your databases before you can upgrade to a version that does not include it.
David J.
В списке pgsql-bugs по дате отправления: