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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: linreg(at)gmx(dot)net, 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-28 15:56:44
Message-ID: 20210128155644.GB14227@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-01-28 16:44:09 Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails
Previous Message Tom Lane 2021-01-28 15:43:45 Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed