| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name>, david(dot)g(dot)johnston(at)gmail(dot)com |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix output of zero privileges in psql |
| Date: | 2023-10-16 15:56:10 |
| Message-ID: | 28a1d403ad2499865a5da1be9dc719b1218f8a8f.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2023-10-14 at 02:45 +0200, Erik Wienhold wrote:
> On 2023-10-09 09:54 +0200, Laurenz Albe write:
> >
> > I tinkered a bit with your documentation. For example, the suggestion to
> > "\pset null" seemed to be in an inappropriate place. Tell me what you think.
>
> +1 You're right to put that sentence right after the explanation of
> empty privileges.
Thanks for looking.
David, how do you feel about this? I am wondering whether to set this patch
"ready for committer" or not.
There is Tom wondering upthread whether changing psql's behavior like that
is too much of a compatibility break or not, but I guess it is alright to
leave that final verdict to a committer.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Banck | 2023-10-16 16:06:40 | Re: Rename backup_label to recovery_control |
| Previous Message | Laurenz Albe | 2023-10-16 15:48:43 | Re: Requiring recovery.signal or standby.signal when recovering with a backup_label |