Re: Things I don't like about \du's "Attributes" column - Mailing list pgsql-hackers

From Pavel Luzanov
Subject Re: Things I don't like about \du's "Attributes" column
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: Things I don't like about \du's "Attributes" column  ("David G. Johnston" <[email protected]>)
Responses Re: Things I don't like about \du's "Attributes" column
List pgsql-hackers
On 16.04.2024 01:06, David G. Johnston wrote:
At this point I'm on board with retaining the \dr charter of simply being an easy way to access the detail exposed in pg_roles with some display formatting but without any attempt to convey how the system uses said information.  Without changing pg_roles.  Our level of effort here, and degree of dependence on superuser, doesn't seem to be bothering people enough to push more radical changes here through and we have good improvements that are being held up in the hope of possible perfection.
I have similar thoughts.
I decided to wait for the end of feature freeze and propose a simpler version
of the patch for v18, without changes in pg_roles.
I hope to send a new version soon.

But about \dr. Is it a typo and you mean \du & \dg?
If we were choosing a name for the command now, then \dr would be ideal:
\dr - display roles
\drg - display role grants

But the long history of \du & \dg prevents from doing so, and creating a third option is too excessive.
-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Typo about the SetDatatabaseHasLoginEventTriggers?
Next
From: Amit Kapila
Date:
Subject: Re: Slow catchup of 2PC (twophase) transactions on replica in LR