Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17 - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Date
Msg-id CAKFQuwYL62ft-S1deUfb5-f8KRZbNbg1emqtEwsSTYib6Juktg@mail.gmail.com
Whole thread Raw
In response to BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17  (PG Bug reporting form <noreply@postgresql.org>)
Responses RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
List pgsql-bugs
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 by date:

Previous
From: Todd Brandys
Date:
Subject: Re: BUG #18647: INSERT statements execute functions twice.
Next
From: PG Bug reporting form
Date:
Subject: BUG #18650: rhel-8-aarch64 yum repository for Postgres 13 is missing repodata