Date: Tue, 29 Aug 2023 21:50:30 +0200 (CEST)
From: Erik Wienhold <ewie@ewie.name>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stuart McGraw <smcg4191@mtneva.com>, pgsql-general@lists.postgresql.org
Message-ID: <2094101432.333909.1693338630182@office.mailbox.org>
In-Reply-To: <31246.1693337238@sss.pgh.pa.us>
References: <96d6885a-5e25-9ae8-4a1a-d7e557a5fe9c@mtneva.com>
 <1166048641.281962.1693308151542@office.mailbox.org>
 <1006397.1693318485@sss.pgh.pa.us>
 <efdd465d-a795-6188-7f71-7cdb4b2be031@mtneva.com>
 <1550267563.330669.1693335893138@office.mailbox.org>
 <31246.1693337238@sss.pgh.pa.us>
Subject: Re: Restoring default privileges on objects
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Importance: Normal
Archived-At: <https://www.postgresql.org/message-id/2094101432.333909.1693338630182%40office.mailbox.org>
Precedence: bulk

> On 29/08/2023 21:27 CEST Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

+1

> 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.

Looks like all commands in src/bin/psql/describe.c set nullPrint = NULL.  Has
been that way since at least 1999.

--
Erik