Re: [PATCH v2] use has_privs_for_role for predefined roles - Mailing list pgsql-hackers

From Joshua Brindle
Subject Re: [PATCH v2] use has_privs_for_role for predefined roles
Date
Msg-id CAGB+Vh4Potn7UQhziej9a6SW=6RR0gPA0xx9GGbSmmbOp1=vOQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH v2] use has_privs_for_role for predefined roles  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Feb 9, 2022 at 3:58 PM Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Wed, Feb 9, 2022 at 1:13 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> > I do wonder if users find the differences between predefined roles and role
> > attributes confusing.  INHERIT doesn't govern role attributes, but it will
> > govern predefined roles when this patch is applied.  Maybe the role
> > attribute system should eventually be deprecated in favor of using
> > predefined roles for everything.  Or perhaps the predefined roles should be
> > converted to role attributes.
>
> I couldn't agree more. Apparently it's even confusing to developers,
> because otherwise (1) we wouldn't have the problem the patch proposes
> to fix in the first place and (2) I would have immediately been
> convinced of the value of the patch once it showed up. Since those
> things didn't happen, this is apparently confusing to (1) whoever
> wrote the code that this patch fixes and (2) me.
>

My original patch removed is_member_of to address #1 above, but that
was rejected[1]. There is now a warning in the header beside it to
hopefully dissuade improper usage going forward.

1. https://www.postgresql.org/message-id/254275.1635357633%40sss.pgh.pa.us



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: decoupling table and index vacuum
Next
From: Andres Freund
Date:
Subject: wrong fds used for refilenodes after pg_upgrade relfilenode changes Reply-To: