pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: GMX LINREG <linreg@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Date: Fri, 29 Jan 2021 18:38:18 +0100
Message-ID: <5448993.DvuYhMxLoT@wolfclan.ang.de> (raw)
In-Reply-To: <2815190.1611941374@sss.pgh.pa.us>
References: <16843-174d3e5b66729a60@postgresql.org>
	<7912997.NyiUUSuA9g@wolfclan.ang.de>
	<2815190.1611941374@sss.pgh.pa.us>

Am Freitag, 29. Januar 2021, 18:29:34 CET schrieb Tom Lane:
> Looking at this more closely, it seems like there must be something broken
> about the plperlu extension in the source database.  We see
> 
> pg_restore: erstelle EXTENSION »plperlu«
> pg_restore: erstelle COMMENT »EXTENSION "plperlu"«
> pg_restore: erstelle PROCEDURAL LANGUAGE »plperlu«
> pg_restore: in Phase PROCESSING TOC:
> pg_restore: in Inhaltsverzeichniseintrag 2151; 2612 16427 PROCEDURAL
> LANGUAGE plperlu postgres pg_restore: Fehler: could not execute query:
> FEHLER:  Sprache »plperlu« existiert nicht Die Anweisung war: CREATE OR
> REPLACE PROCEDURAL LANGUAGE "plperlu";
> 
> but a binary-upgrade dump should have dumped the plperlu support functions
> before the procedural language object.  And the CREATE PROCEDURAL LANGUAGE
> command should have included explicit HANDLER etc clauses.  Both things
> could be explained by supposing that pg_dump didn't see the support
> functions as part of the extension, but why not?
> 
> It might be interesting to check the results of "\dx+ plperlu" in the
> source database.
> 
> 			regards, tom lane
Hello

output from source database:
botdb=# \dx+ plperlu
Objekte in Erweiterung »plperlu«
 Objektbeschreibung 
--------------------
 language plperlu

thomas steffen








view thread (14+ messages)  latest in thread

Message-ID: <5448993.DvuYhMxLoT@wolfclan.ang.de>
Permalink:  ../5448993.DvuYhMxLoT@wolfclan.ang.de/
Also on:    postgresql.org/message-id/5448993.DvuYhMxLoT@wolfclan.ang.de

 · 

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: linreg@gmx.net, tgl@sss.pgh.pa.us, bruce@momjian.us, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
  In-Reply-To: <5448993.DvuYhMxLoT@wolfclan.ang.de>

* 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