Re: Usability fail with psql's \dp command - Mailing list pgsql-hackers

From Isaac Morland
Subject Re: Usability fail with psql's \dp command
Date
Msg-id CAMsGm5cE6XVYJJDdj9KwaFJ1tegx8-CJED8uH_k0ofNxy+cPtQ@mail.gmail.com
Whole thread Raw
In response to Re: Usability fail with psql's \dp command  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On 31 July 2018 at 15:02, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
[....] 
Indeed, all \d* which display perms have the empty/default confusion:

  \dp \ddp \des \dew \l \dn \db \df \dT \dD \dL

I fixed them all to display the default acl in the patch I just sent.

I also noticed that although large objects have permissions, they are not printed by any backslash commands.

Also using \df to display permissions is inconvenient because \df+ is required, which also shows function source code which usually overwhelms the rest of the display. Any chance we can remove the source code column from \df now that we have \sf? I usually avoid looking at function permissions and select directly from pg_proc if I absolutely must know.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade from 9.4 to 10.4
Next
From: Bruce Momjian
Date:
Subject: Re: Online enabling of checksums