Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION - Mailing list pgsql-bugs

From Aksel Allas
Subject Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION
Date
Msg-id CABnLe_AtD_M66oYkzgzxTe2fyi7rUwLZb1oU7Ug1y5jv==SKTQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION
List pgsql-bugs
Thanks for the quick reply!

So it's not possible to fully use pg_dump without manually altering the output of pg_dump in managed postgreSQL cases?

Probably pg_dump not supporting managed postgresql makes sense.

On Tue, Dec 12, 2023 at 2:14 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2023-12-12 at 10:43 +0000, PG Bug reporting form wrote:
> When making a dump from PostgreSQL 14 and using it in PostgreSQL 15 with a
> user that has no superuser access (e.g. cloud environments), then we run
> into the following line from
> https://www.postgresql.org/docs/15/sql-alterfunction.html
>
> > To alter the owner, you must also be a direct or indirect member of the
> new owning role, and that role must have CREATE privilege on the function's
> schema.

That is working as it should.

Yours,
Laurenz Albe


pgsql-bugs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Issue with pg_get_functiondef
Next
From: Dean Rasheed
Date:
Subject: Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access