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-11-20 04:21:31
Message-ID: CAKFQuwaSk6d5eAAhGnP7H3ZuoV8d66mV2wxcCPigG5CQijcByw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, November 19, 2024, Bing Xu <bing(dot)xu(dot)uh(at)fujifilm(dot)com> wrote:

> Thank you for your response.
>
> >https://www.postgresql.org/docs/current/release-17.html#
> RELEASE-17-MIGRATION
>
> Is it the following passage?
>
>
Yes

> Instead of letting pg_upgrade.exe automatically uninstall adminpack.
>
> Is my understanding correct?
>
>
pg_upgrade will never uninstall anything. It installs whatever is in the
source cluster unconditionally. Except catalogs, which are instead built in
the new cluster during initdb.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-11-20 04:23:13 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Previous Message Bing Xu 2024-11-20 04:05:26 RE: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17