Re: Restoring default privileges on objects - Mailing list pgsql-general

From Tom Lane
Subject Re: Restoring default privileges on objects
Date
Msg-id 31246.1693337238@sss.pgh.pa.us
Whole thread Raw
In response to Re: Restoring default privileges on objects  (Erik Wienhold <ewie@ewie.name>)
Responses Re: Restoring default privileges on objects  (Erik Wienhold <ewie@ewie.name>)
Re: Restoring default privileges on objects  (Stuart McGraw <smcg4191@mtneva.com>)
List pgsql-general
Erik Wienhold <ewie@ewie.name> writes:
> On 29/08/2023 18:43 CEST Stuart McGraw <smcg4191@mtneva.com> wrote:
>> Shouldn't psql put *something* (like "(default)" or "-") in the
>> "Access privileges" column to indicate that?  Or conversely,
>> something (like "(none)"?) in the revoked case?

> Indeed, that's confusing.  Command \dp always prints null as empty string [1].
> So \pset null '(null)' has no effect.

Yeah, perhaps.  The reason it so seldom comes up is that a state of
zero privileges is extremely rare (because it's useless in practice).

That being the case, if we were to do something about this, I'd vote
for changing the display of zero-privileges to "(none)" or something
along that line, rather than changing the display of NULL, which
people are accustomed to.

Fixing \dp to honor "\pset null" for this might be a reasonable
thing to do too.  I'm actually a bit surprised that that doesn't
work already.

            regards, tom lane



pgsql-general by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: Restoring default privileges on objects
Next
From: Erik Wienhold
Date:
Subject: Re: Restoring default privileges on objects