| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Subject: | Re: How about a psql backslash command to show GUCs? |
| Date: | 2022-04-07 15:10:14 |
| Message-ID: | CAKFQuwbHS2thR7eV2q+vkT3ZPa1VLrAZg-H3k7f8pUxaee19kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 7, 2022 at 7:56 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>
>
> Maybe to appeal to all crowds, we say "list configuration parameters
> > (GUCs)"?
>
> I'm in the camp that says that GUC is not an acronym we wish to expose
> to end users.
>
>
I am too. In any case, either go all-in with GUC (i.e., \dG or \dguc) or
pretend it doesn't exist - an in-between position is unappealing.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josef Šimánek | 2022-04-07 15:15:24 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | Tom Lane | 2022-04-07 14:55:58 | Re: How about a psql backslash command to show GUCs? |