| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Usability fail with psql's \dp command |
| Date: | 2018-07-31 19:30:22 |
| Message-ID: | CAMsGm5cE6XVYJJDdj9KwaFJ1tegx8-CJED8uH_k0ofNxy+cPtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 31 July 2018 at 15:02, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-07-31 19:45:35 | Re: Online enabling of checksums |
| Previous Message | Tom Lane | 2018-07-31 19:26:47 | Re: pg_upgrade from 9.4 to 10.4 |