Re: Usability fail with psql's \dp command

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


>> So those are definitely different privilege states, but they look
>> the same.
>
> Please find attached a patch to fix this. Would this be a
> back-patchable bug?

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.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-07-29 00:43:29 pgsql: Refactor geometric functions and operators
Previous Message Fabien COELHO 2018-07-28 23:59:00 Re: Removing useless \. at the end of copy in pgbench