From: Euler Taveira <euler@eulerto.com>
To: Bing Xu <bing.xu.uh@fujifilm.com>
To: David G. Johnston <david.g.johnston@gmail.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
Date: Wed, 09 Oct 2024 21:56:00 -0300
Message-ID: <b8d6cc91-fe12-4786-ae39-06d80d8110d5@app.fastmail.com> (raw)
In-Reply-To: <PH0PR08MB77481A8BEAF278E92E6E8119B97F2@PH0PR08MB7748.namprd08.prod.outlook.com>
References: <18635-7a3e4e903d99c814@postgresql.org>
<CAKFQuwap+BUzOvd==rOifJ6D5j1-1N_6qBGNfjgouoZJg8e7DQ@mail.gmail.com>
<PH0PR08MB77481A8BEAF278E92E6E8119B97F2@PH0PR08MB7748.namprd08.prod.outlook.com>
On Wed, Oct 9, 2024, at 6:17 AM, Bing Xu wrote:
> 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?
>
... because this list can be large along the years. That's why pg_upgrade adopts
loadable_libraries.txt file that reports the loadable module failures. You
should run pg_upgrade with --check option and if there is an error, check the
referred file.
8<----------------------------------------------------------------------------8<
$ /h/pg17/bin/pg_upgrade -b /h/pg16/bin -B /h/pg17/bin -d /tmp/foo16 -D /tmp/foo17 --check
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking data type usage ok
Checking for presence of required libraries fatal
Your installation references loadable libraries that are missing from the
new installation. You can add these libraries to the new installation,
or remove the functions using them from the old installation. A list of
problem libraries is in the file:
/tmp/foo17/pg_upgrade_output.d/20241009T213155.590/loadable_libraries.txt
Failure, exiting
$ cat /tmp/foo17/pg_upgrade_output.d/20241009T213948.961/loadable_libraries.txt
could not load library "$libdir/adminpack": ERROR: could not access file "$libdir/adminpack": No such file or directory
In database: postgres
8<----------------------------------------------------------------------------8<
It is highly recommended to read all release notes [1] from version X+1 to Y
where X is your current version and Y is your new version before upgrading.
In this particular case (adminpack), even though it belongs to Additional
Modules section, I would add it to Migration to Version 17 because it is an
incompatibility with the previous releases. Well, this ship has already sailed
and it is documented (lines below).
[1] https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-MODULES
--
Euler Taveira
EDB https://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: euler@eulerto.com, bing.xu.uh@fujifilm.com, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18635: " $libdir/adminpack could not be loaded" error with pg_upgrade to PostgreSQL17
In-Reply-To: <b8d6cc91-fe12-4786-ae39-06d80d8110d5@app.fastmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox