pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: linreg@gmx.net
Subject: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Date: Thu, 28 Jan 2021 12:53:31 +0000
Message-ID: <16843-174d3e5b66729a60@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16843
Logged by:          Thomas Steffen
Email address:      linreg@gmx.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



view thread (14+ messages)  latest in thread

Message-ID: <16843-174d3e5b66729a60@postgresql.org>
Permalink:  ../16843-174d3e5b66729a60@postgresql.org/
Also on:    postgresql.org/message-id/16843-174d3e5b66729a60@postgresql.org

 · 

reply

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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, linreg@gmx.net
  Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
  In-Reply-To: <16843-174d3e5b66729a60@postgresql.org>

* 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