Postgres Pro
Downloads
Home   >   mailing lists

Re: How about a psql backslash command to show GUCs? - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: How about a psql backslash command to show GUCs?
Date
Msg-id CAKFQuwbHS2thR7eV2q+vkT3ZPa1VLrAZg-H3k7f8pUxaee19kQ@mail.gmail.com
Whole thread Raw
In response to Re: How about a psql backslash command to show GUCs?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: How about a psql backslash command to show GUCs?  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
Tree view
On Thu, Apr 7, 2022 at 7:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Jonathan S. Katz" <jkatz@postgresql.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.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: How about a psql backslash command to show GUCs?
Next
From: Josef Šimánek
Date:
Subject: Re: How about a psql backslash command to show GUCs?