2009/10/21 Peter Eisentraut <peter_e@gmx.net>:
> Could someone clarify why this (from PG 8.4)
>
> # \du
> List of roles
> Role name | Attributes | Member of
> ---------------+-------------+------------
> admin | Create role | {}
> : Create DB
> postgres | Superuser | {}
> : Create role
> : Create DB
> someotheruser | | {}
> someuser | | {}
>
> is an improvement over this (from PG 8.3)
>
> # \du
> List of roles
> Role name | Superuser | Create role | Create DB | Connections |
> ---------------+-----------+-------------+-----------+-------------+------------
> admin | no | yes | yes | no limit | {}
> postgres | yes | yes | yes | no limit | {}
> someotheruser | no | no | no | no limit | {}
> someuser | no | no | no | no limit | {}
> (4 rows)
>
> The way I see it, a perfectly clear, complete, and legible table has
> been turned into a denormalized, unreadable, and ugly pile of ASCII
> salad that moreover wastes valuable vertical screen space instead of
> using the abundant horizontal screen space.
>
I can see a possible advantage in that there is more room to list the
membership items (although I can't see that being useful most of the
time), and it also provides flexibility by providing an undefined list
of attributes compared to a defined list. For example, the new format
allows the display of "No inheritance", something not shown in the old
format.
However, if that is the limit of how this more flexible approach is
being taken advantage of, I'd tend to agree that the previous format
was fine.
Thom