Re: Fix output of zero privileges in psql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
Erik Wienhold <ewie@ewie.name>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-10-24T02:43:40Z
Lists: pgsql-hackers
Laurenz Albe <laurenz.albe@cybertec.at> writes: > On Mon, 2023-10-23 at 11:37 -0700, David G. Johnston wrote: >> I do believe that we should be against exposing, like in this case, any internal >> implementation detail that encodes something (e.g., default privileges) as NULL >> in the catalogs, to the user of the psql meta-commands. > Sure, it would be best to hide this implementation detail from the user. > The correct way to do that would be to fake an ACL entry like "laurenz=arwdDxt/laurenz" > if there is a NULL in the catalog, but that would add a ton of special-case > code to psql, which does not look appealing at all. For better or worse, that *is* the backend's catalog representation, and I don't think that psql would be doing our users a service by trying to obscure the fact. They'd run into it anyway the moment they look at the catalogs with anything but a \d-something command. regards, tom lane
Commits
-
Improve default and empty privilege outputs in psql.
- d1379ebf4c2d 17.0 landed