Re: pg_upgrade is failed for 'plpgsql_call_handler' handler

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade is failed for 'plpgsql_call_handler' handler
Date: 2021-06-03 10:54:48
Message-ID: B1946B73-973E-4327-9CF8-FBD5573C40D0@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 3 Jun 2021, at 11:53, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:

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

This isn't really a pg_upgrade issue but a pg_dump issue. The handler, inline
nd validator functions will be looked up among the functions loaded into
pg_dump and included in the CREATE LANGUAGE statement. However, iff they are
in pg_catalog then they wont be found (pg_catalog is excluded in getFuncs) and
a bare CREATE LANGUAGE statement will be emitted. This bare statement will
then be interpreted as CREATE EXTENSION.

This is intentional since the language template work in 8.1, before then
pg_dump would look up support functions in pg_catalog.

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-06-03 11:17:05 Re: Are we missing (void) when return value of fsm_set_and_search is ignored?
Previous Message Bharath Rupireddy 2021-06-03 10:54:28 Are we missing (void) when return value of fsm_set_and_search is ignored?