public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pavel Luzanov <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: David Zhang <[email protected]>
Cc: [email protected] <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: psql: Add role's membership options to the \du+ command
Date: Sun, 25 Jun 2023 17:44:51 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwad6E0C+=_uk0CFK-x1jfFNeyOOmmaMObDxC5=nyF7Gvg@mail.gmail.com>
References: <[email protected]>
<CAKFQuwanYpV_0quPhRMpVoyUew4-4to0u1E0uXMNY4=ODPZHWQ@mail.gmail.com>
<[email protected]>
<CAKFQuwZXQP7ox0jsa+AqKa-4MkTpd2VypJm9dkXsk+6wKEQ2Gg@mail.gmail.com>
<[email protected]>
<[email protected]>
<CAKFQuwZiomZFLd5zK=feCjY7Weefvce1MR+k38wyBMbaP2ASsg@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<CAKFQuwa7EDaN6wzK4TSym8KrN3oSXJmYNEDyWNGRd5qw1pyUFQ@mail.gmail.com>
<[email protected]>
<CAKFQuwZ7RDkUMAtBE1hkcpsbEfnRQA__Rii6cW-2fipsHKF6gg@mail.gmail.com>
<[email protected]>
<CAKFQuwZxCUs=o-jWRUaHOoxBxpB1OTTVSvbz_0ivoSs4UM6KiA@mail.gmail.com>
<[email protected]>
<CAKFQuwad6E0C+=_uk0CFK-x1jfFNeyOOmmaMObDxC5=nyF7Gvg@mail.gmail.com>
On 24.06.2023 18:57, David G. Johnston wrote:
> On Sat, Jun 24, 2023 at 8:11 AM Pavel Luzanov
> <[email protected]> wrote:
>
> There are two commands showing the same information about roles:
> \du and
> \dr.
>
>
> I would add \dr as the new official command to complement adding \drg
> and deprecate both \du and \dg. Though actual removal and
> de-documenting doesn't seem like a good idea. But if we ever did
> assign something non-role to \dr it would be very confusing.
It's my mistake and inattention. I was thinking about '\du' and '\dg',
and wrote about '\du' and '\dr'.
I agree that \dr and \drg the best names.
So, now concentrating on implementing \drg.
> * The new meta-command will also make sense for versions <16.
> The ADMIN OPTION is available in all supported versions.
>
>
> Doesn't every role pre-16 gain SET permission? We can also deduce
> whether the grant provides INHERIT based upon the attribute of the
> role in question.
Indeed! I will do so.
>
>
> * The new meta-command will not show all roles. It will only show the
> roles included in other roles.
> To show all roles you need to add an outer join between pg_roles and
> pg_auth_members.
> But all columns except "role" will be left blank. Is it worth
> doing this?
>
>
> I'm inclined to want this. I would be good when specifying a role to
> filter upon that all rows that do exist matching that filter end up in
> the output regardless if they are standalone or not.
Ok
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: psql: Add role's membership options to the \du+ command
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox