| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "bing(dot)xu(dot)uh(at)fujifilm(dot)com" <bing(dot)xu(dot)uh(at)fujifilm(dot)com>, "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-09-27 13:47:20 |
| Message-ID: | CAKFQuwap+BUzOvd==rOifJ6D5j1-1N_6qBGNfjgouoZJg8e7DQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thursday, September 26, 2024, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18635
> Logged by: xu bing
> Email address: bing(dot)xu(dot)uh(at)fujifilm(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-09-27 14:00:08 | Re: BUG #18636: I am seeing a difference in behavior between 13.12 and 15.6 for full text searching |
| Previous Message | PG Bug reporting form | 2024-09-27 13:28:18 | BUG #18636: I am seeing a difference in behavior between 13.12 and 15.6 for full text searching |