| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix output of zero privileges in psql |
| Date: | 2023-10-08 04:14:12 |
| Message-ID: | 30ef7918c8f1a0b811d11350e7f658a3c3439441.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2023-10-07 at 20:41 +0200, Erik Wienhold wrote:
> > If you are happy enough with my patch, shall we mark it as ready for
> > committer?
>
> I amended your patch to also document the effect of \pset null in this
> case. See the attached v2.
+1
If you mention in ddl.sgml that you can use "\pset null" to distinguish
default from no privileges, you should mention that this only works with
psql. Many people out there don't use psql.
Also, I'm not sure if "zero privileges" will be readily understood by
everybody. Perhaps "no privileges at all, even for the object owner"
would be a better wording.
Perhaps it would also be good to mention this in the psql documentation.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-10-08 05:15:18 | Re: pg_upgrade --copy-file-range |
| Previous Message | Quan Zongliang | 2023-10-08 03:50:43 | Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block |