Re: Fix output of zero privileges in psql
От | Tom Lane |
---|---|
Тема | Re: Fix output of zero privileges in psql |
Дата | |
Msg-id | 3977263.1697831824@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Fix output of zero privileges in psql ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: Fix output of zero privileges in psql
|
Список | 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
В списке pgsql-hackers по дате отправления: