Re: Usability fail with psql's \dp command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: David Fetter <david(at)fetter(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Usability fail with psql's \dp command
Date: 2018-07-29 02:35:50
Message-ID: 998.1532831750@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
> My 0.02¤: this creates an exception for anyone trying to parse the output.
> I would have preferred empty logically meaning no rights, and the default
> being spelled out explicitely.

Uh, who'd be trying to parse the output of \dp?

The reason we provide psql's -E option is so that people can look at the
underlying queries and adapt them to their own purposes. In many cases,
that would include stripping out provisions that make the output more
human-friendly and less machine-friendly. (Localization of output words
is one obvious example of things that psql does that are quite
machine-parsing-unfriendly.) This seems to me to be another such case.

We could certainly consider the explicit-default approach (and it's one
of the options I suggested), but to my mind we should evaluate the
options entirely on what humans find readable, with exactly zero weight
to machine readability.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-07-29 06:14:56 Re: Postgres, fsync, and OSs (specifically linux)
Previous Message Tomas Vondra 2018-07-29 01:54:18 Re: [PATCH] Improve geometric types