Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
Date: 2024-07-08 19:58:06
Message-ID: CAKFQuwaSk4Ftn52X3aup9upDkurAunTHLB1XtZb0Pkzs7TTYUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 8, 2024 at 12:23 PM Christophe Pettus <xof(at)thebuild(dot)com> wrote:

>
> This is more curiosity than anything else. In the v16 role system, is
> there actually any reason to grant membership in a role to a different
> role, but with SET FALSE, INHERIT FALSE, and ADMIN FALSE? Does the role
> granted membership gain any ability it didn't have before in that case?
>
>
That scenario is allowed but provides no useful in-server behavior. I
suppose the membership presence/absence could be given external meaning by
a DBA. Personally, I'd just add a metric on the server counting these and
alert if it is ever non-zero.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2024-07-08 20:14:21 Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
Previous Message Ruben Morais 2024-07-08 19:57:04 Re: Upgrading from v12.7 to v15.7