| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stuart McGraw <smcg4191(at)mtneva(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Restoring default privileges on objects |
| Date: | 2023-08-29 19:50:30 |
| Message-ID: | 2094101432.333909.1693338630182@office.mailbox.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> On 29/08/2023 21:27 CEST Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan Stange | 2023-08-29 20:09:16 | Re: [INTERNET] Re: auto vacuum question |
| Previous Message | Tom Lane | 2023-08-29 19:27:18 | Re: Restoring default privileges on objects |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-08-29 20:40:08 | Re: tablecmds.c/MergeAttributes() cleanup |
| Previous Message | Tom Lane | 2023-08-29 19:27:18 | Re: Restoring default privileges on objects |