Re: pg_upgrade fails with an error "object doesn't exist" - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: pg_upgrade fails with an error "object doesn't exist"
Date
Msg-id 5AA0B9D8-9AE5-4854-A2BE-BBE8060A48AB@yesql.se
Whole thread Raw
In response to Re: pg_upgrade fails with an error "object doesn't exist"  (Vaibhav Dalvi <vaibhav.dalvi@enterprisedb.com>)
Responses Re: pg_upgrade fails with an error "object doesn't exist"
Re: pg_upgrade fails with an error "object doesn't exist"
List pgsql-hackers
> On 16 Jun 2025, at 09:29, Vaibhav Dalvi <vaibhav.dalvi@enterprisedb.com> wrote:

> I'm able to create the object as shown in the below:
>
> postgres=# CREATE OR REPLACE FUNCTION pg_catalog.nont_ext_func() RETURNS char AS $$ BEGIN return 'v'; END; $$
LANGUAGEplpgsql; 
> CREATE FUNCTION
>
> Why can't we strictly restrict object creation in pg_catalog?

Do you have allow_system_table_mods set to ON by any chance?  As Laurenz said,
such creation is already restricted, but it can be circumvented by using said
GUC (which is *not* intended for production usage).

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Vaibhav Dalvi
Date:
Subject: Re: pg_upgrade fails with an error "object doesn't exist"
Next
From: Daniel Gustafsson
Date:
Subject: Re: Possibly hard-to-read message