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

From David G. Johnston
Subject Re: Things I don't like about \du's "Attributes" column
Date
Msg-id CAKFQuwaPfA+eO45VqeRk7WWi2=RQxeF999JmC1Z8Jmrvxw4g8A@mail.gmail.com
Whole thread Raw
In response to Re: Things I don't like about \du's "Attributes" column  ("Wen Yi" <wen-yi@qq.com>)
List pgsql-hackers
On Sat, Apr 13, 2024 at 7:02 PM Wen Yi <wen-yi@qq.com> wrote:
I think we can change the output like this:

postgres=# \du
                                List of roles
 Role name | Login | Attributes  | Password | Valid until | Connection limit
-----------+-------+-------------+----------+-------------+------------------
 test      |       | Inherit     |          |             |
 test2     | Can   | Inherit     | Has      |             |
 wenyi     | Can   | Superuser  +|          |             |
           |       | Create DB  +|          |             |
           |       | Create role+|          |             |
           |       | Inherit    +|          |             |
           |       | Replication+|          |             |
           |       | Bypass RLS  |          |             |
(3 rows)

And I submit my the patch, have a look?


Why?  I actually am generally open to false being encoded as blank where there are only two possible values, but there is no precedence of choosing something besides 'yes' or 'true' to represent the boolean true value.

Whether Password is truly two-valued is debatable per the ongoing discussion.

David J.

pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Re: make dist using git archive
Next
From: "Joel Jacobson"
Date:
Subject: Optimize numeric.c mul_var() using the Karatsuba algorithm