Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE - Mailing list pgsql-general

From Tom Lane
Subject Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
Date
Msg-id 1221566.1720476530@sss.pgh.pa.us
Whole thread Raw
In response to Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
List pgsql-general
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Mon, Jul 8, 2024 at 2:16 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Pavel Luzanov <p.luzanov@postgrespro.ru> writes:
> On 08.07.2024 22:22, Christophe Pettus 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?

>>> Looks like there is one ability.
>>> Authentication in pg_hba.conf "USER" field via +role syntax.

>> Hmm, if that check doesn't require INHERIT TRUE I'd say it's
>> a bug.

> The code doesn't support that claim.

That doesn't make it not a bug.  Robert, what do you think?  If this
is correct behavior, why is it correct?

            regards, tom lane



pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE
Next
From: Joseph Hammerman
Date:
Subject: SQL: Chaining versus Pipelining