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 03:52:11
Message-ID: CAKFQuwZavjtD08Pmm4F71XPLXqwd2NW8Lv-E7iNxLXahRSkMmA@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:
>
> > You will not find version-specific commentary in the notes for the
> pgupgrade application. We have release notes for them.
>
> Could you please tell me specifically where it is documented?
>
>

https://www.postgresql.org/docs/current/release-17.html#RELEASE-17-MIGRATION

David J.

In response to

Responses

Browse pgsql-bugs by date

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