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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(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-10-09 12:30:17
Message-ID: CAKFQuwYL62ft-S1deUfb5-f8KRZbNbg1emqtEwsSTYib6Juktg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wednesday, October 9, 2024, Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2024-10-09 12:34:38 RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
Previous Message Todd Brandys 2024-10-09 12:26:05 Re: BUG #18647: INSERT statements execute functions twice.