Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed

From: GMX Steffen <steffen(dot)ang(at)gmx(dot)de>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Date: 2021-01-29 13:23:31
Message-ID: 7226587.EvYhyI6sBW@wolfclan.ang.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Am Donnerstag, 28. Januar 2021, 16:56:44 CET schrieben Sie:
> On Thu, Jan 28, 2021 at 10:43:45AM -0500, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > On Thu, Jan 28, 2021 at 10:34:46AM -0500, Tom Lane wrote:
> > >> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > >>> pg_restore: Error: could not execute query: ERROR: Language »plperlu«
> > >>> does
> > >>> not exist
> > >>> The statement was: CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";
> > >>
> > >> It looks like you neglected to install the plperlu package
> > >> (it's probably named something like postgresql-plperl).
> > >
> > > Yeah, I am confused why this was not reported clearly to the user.
> >
> > It is odd that pg_upgrade's checks didn't catch it earlier. But
> > we can't investigate without more info about exactly what Postgres
> > packages are present on the OP's system.
>
> Yes, usually the error report is very clear, we would need to see
> _exactly_ what they saw.

Hello,

to clearify,
- plperl package is already installed (see below).
- command 'CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";' doesn't create a
language object, but just an extension object (see below)

Please note the attached upgrade log file from pg_upgrade "pg_upgrade_dump_16401.log".

OS Packages:
*postgresql*-llvmjit-13-lp152.3.1.noarch
*postgresql*12-pldebugger-1.0+git13.ddbce7b-lp152.1.4.x86_64
*postgresql*12-llvmjit-12.5-lp152.34.1.x86_64
*postgresql*-13-lp152.3.1.noarch
*postgresql*12-docs-12.5-lp152.34.1.noarch
*postgresql*12-contrib-12.5-lp152.34.1.x86_64
*postgresql*13-plperl-13.1-lp152.16.1.x86_64
*postgresql*12-server-12.5-lp152.34.1.x86_64
*postgresql*-docs-13-lp152.3.1.noarch
*postgresql*12-12.5-lp152.34.1.x86_64
*postgresql*12-pg_qualstats-2.0.2-lp152.2.3.x86_64
*postgresql*12-ip4r-2.4.1+git1.5f9ce88-lp152.8.2.x86_64
*postgresql*-server-13-lp152.3.1.noarch
*postgresql*12-pg_qualstats-llvmjit-2.0.2-lp152.2.3.x86_64
*postgresql*13-docs-13.1-lp152.16.1.noarch
*postgresql*13-server-13.1-lp152.16.1.x86_64
*postgresql*-contrib-13-lp152.3.1.noarch
*postgresql*12-ip4r-llvmjit-2.4.1+git1.5f9ce88-lp152.8.2.x86_64
*postgresql*13-13.1-lp152.16.1.x86_64
*postgresql*13-llvmjit-13.1-lp152.16.1.x86_64
*postgresql*-plperl-13-lp152.3.1.noarch
*postgresql*12-pldebugger-llvmjit-1.0+git13.ddbce7b-lp152.1.4.x86_64
*postgresql*13-contrib-13.1-lp152.16.1.x86_64

Output from failed database upgrade:
botdb=# \dL

Attachment Content-Type Size
pg_upgrade_dump_16401.log text/x-log 2.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message linreg 2021-01-29 13:29:09 Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Previous Message Kyotaro Horiguchi 2021-01-29 07:14:09 Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data