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

From: Aksel Allas <allasaksel(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION
Date: 2023-12-12 12:51:02
Message-ID: CABnLe_AtD_M66oYkzgzxTe2fyi7rUwLZb1oU7Ug1y5jv==SKTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)albe(at)cybertec(dot)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
>
>
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2023-12-12 13:16:09 Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
Previous Message Laurenz Albe 2023-12-12 12:18:49 Re: Issue with pg_get_functiondef