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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: linreg(at)gmx(dot)net
Subject: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Date: 2021-01-28 12:53:31
Message-ID: 16843-174d3e5b66729a60@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16843
Logged by: Thomas Steffen
Email address: linreg(at)gmx(dot)net
PostgreSQL version: 13.1
Operating system: OpenSuse 15.2
Description:

Hello
In the upgrade process with pg_upgrade ( as user postgres) following error
occured:
Translated from German!
---- SNIPPET ----
pg_restore: create EXTENSION »plperlu«
pg_restore: create COMMENT »EXTENSION "plperlu"«
pg_restore: create PROCEDURAL LANGUAGE »plperlu«
pg_restore: in Phase PROCESSING TOC:
pg_restore: in Table of contents 2151; 2612 16427 PROCEDURAL LANGUAGE
plperlu postgres
pg_restore: Error: could not execute query: ERROR: Language »plperlu« does
not exist
The statement was: CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";

-- For binary upgrade, handle extension membership the hard way
ALTER EXTENSION "plperlu" ADD LANGUAGE "plperlu";

----- SNIPPET END -----

The last command can not be executed succesfully. ==> ALTER EXTENSION
"plperlu" ADD LANGUAGE "plperlu";
possible cause:
This command "CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";"
does not create a LANGUAGE object. It creates only the extension object
plperlu!
This means the language cannot be added to this extension.

i think the workaround with
> CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";
> ALTER EXTENSION "plperlu" ADD LANGUAGE "plperlu";
for
> CREATE EXTENSION "plperlu";
is not necessary.

best regards

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-01-28 13:16:32 BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data
Previous Message Peter Eisentraut 2021-01-28 12:31:46 Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails