Re: pg_upgrade is failed for 'plpgsql_call_handler' handler
От | Daniel Gustafsson |
---|---|
Тема | Re: pg_upgrade is failed for 'plpgsql_call_handler' handler |
Дата | |
Msg-id | B1946B73-973E-4327-9CF8-FBD5573C40D0@yesql.se обсуждение исходный текст |
Ответ на | pg_upgrade is failed for 'plpgsql_call_handler' handler (tushar <tushar.ahuja@enterprisedb.com>) |
Ответы |
Re: pg_upgrade is failed for 'plpgsql_call_handler' handler
|
Список | pgsql-hackers |
> On 3 Jun 2021, at 11:53, tushar <tushar.ahuja@enterprisedb.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/
В списке pgsql-hackers по дате отправления: