pg_upgrade is failed for 'plpgsql_call_handler' handler - Mailing list pgsql-hackers

From tushar
Subject pg_upgrade is failed for 'plpgsql_call_handler' handler
Date
Msg-id 6d78613b-d87e-2783-608f-6c13f06d497f@enterprisedb.com
Whole thread Raw
Responses Re: pg_upgrade is failed for 'plpgsql_call_handler' handler  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Hi,

In one of my testing scenario, i found pg_upgrade is failed for 
'plpgsql_call_handler' handler

Steps to reproduce - ( on any supported version of PG)

Perform initdb ( ./initdb -D  d1 ;  ./initdb -D d2)

Start d1 cluster(./pg_ctl -D d1 start) , connect to postgres (./psql 
postgres)  and create this language

postgres=# CREATE TRUSTED LANGUAGE plspl_sm HANDLER plpgsql_call_handler;
CREATE LANGUAGE

stop the server (./pg_ctl -D d1 stop)

perform pg_upgrade ( ./pg_upgrade -d d1 -D d2 -b . B .)

will fail with these message

pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 825; 2612 16384 PROCEDURAL LANGUAGE plspl_sm edb
pg_restore: error: could not execute query: ERROR:  could not open 
extension control file 
"/home/edb/pg14/pg/edbpsql/share/postgresql/extension/plspl_sm.control": 
No such file or directory
Command was: CREATE OR REPLACE PROCEDURAL LANGUAGE "plspl_sm";

is this expected ?

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company




pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions