Re: Fix output of zero privileges in psql
| От | David G. Johnston |
|---|---|
| Тема | Re: Fix output of zero privileges in psql |
| Дата | |
| Msg-id | CAKFQuwYinjuJO7yPjGcDfW=CPtJh_6f7pSjZa4aiCmNoRwu09Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Fix output of zero privileges in psql (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Fix output of zero privileges in psql
|
| Список | pgsql-hackers |
On Fri, Oct 20, 2023 at 12:34 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> I am not sure how to proceed. Perhaps it would indeed be better to have
> two competing commitfest entries. Both could be "ready for committer",
> and the committers can decide what they prefer.
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. At least, the existing \pset null patch doesn't purport to fix anything that would become not applicable if the (none) patch goes in. I.e., at present they are mutually exclusive.
David J.
В списке pgsql-hackers по дате отправления: