Re: incorrect pg_dump output due to not handling dropped roles correctly - Mailing list pgsql-bugs

From Stephen Frost
Subject Re: incorrect pg_dump output due to not handling dropped roles correctly
Date
Msg-id CAOuzzgqSoB3bAe8VcYPCvvk=pfBmLz4kmA5L8wGsTqPatuRg0w@mail.gmail.com
Whole thread Raw
In response to Re: incorrect pg_dump output due to not handling dropped rolescorrectly  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: incorrect pg_dump output due to not handling dropped roles correctly
List pgsql-bugs
Greetings,

On Fri, Jan 17, 2020 at 16:26 Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Stephen, are you intending to get this bug fixed?

I had been hoping to get some kind of feedback or even a response regarding to the email I posted about what’s going on and how we might want to think about handling this situation.

In particular- should we really be setting default privileges for objects that are being created by an extension, at all?  The more I think about it, the less I like it, particularly when we start to think about the trusted extension work that Tom’s doing.

In short, I’m leaning towards the argument that this was a missing check in the default ACL code to explicitly *not* add default privileges on objects that are being created by an extension.  With such a check, the entire wouldn’t end up in pg_init_privs and the issue that started this thread wouldn’t happen.

Thanks,

Stephen

pgsql-bugs by date:

Previous
From: Kieran McCusker
Date:
Subject: Re: BUG #16223: Performance regression between 11.6 and 12.1 in anSQL query with a recursive CTE based on function
Next
From: Tom Lane
Date:
Subject: Re: incorrect pg_dump output due to not handling dropped roles correctly