Re: Fix output of zero privileges in psql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Erik Wienhold <ewie@mailbox.org>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-10-20T19:57:04Z
Lists: pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Fri, Oct 20, 2023 at 12:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> As near as I can tell, doing both things (the \pset null fix and >> substituting "(none)" for empty privileges) would be an acceptable >> answer to everyone who has commented. Let's proceed with both >> patches, or combine them into one if there are merge conflicts. > I'm under the impression that removing the null representation of empty > privileges by making them (none) removes all known \d commands that output > nulls and don't obey \pset null. How so? IIUC the proposal is to substitute "(none)" for empty-string ACLs, not null ACLs. The \pset change should be addressing an independent case. regards, tom lane
Commits
-
Improve default and empty privilege outputs in psql.
- d1379ebf4c2d 17.0 landed