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

From Andrew Dunstan
Subject Re: How about a psql backslash command to show GUCs?
Date
Msg-id 995e06b1-0e50-396e-fce3-934d5e511e27@dunslane.net
Whole thread Raw
In response to Re: How about a psql backslash command to show GUCs?  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: How about a psql backslash command to show GUCs?  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
On 4/6/22 23:25, David Rowley wrote:
> I also find myself querying pg_settings all too often. More typing
> than I'd like.
>
> On Thu, 7 Apr 2022 at 06:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I do agree that \show might be a bad choice, the reason being that
>> the adjacent \set command is for psql variables not GUCs; if we
>> had a \show I'd sort of expect it to be a variant spelling of
>> "\echo :variable".
> I also think \show is not a great choice. I'd rather see us follow the
> \d pattern for showing information about objects in the database.
>
>> "\sc" isn't awful perhaps.
> I think \dG is pretty good. G for GUC.
>


-1 on anything that is based on "GUC", an ancient and now largely
irrelevant acronym. How many developers, let alone users, know what it
stands for?


\dconf seems fine to me


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add index scan progress to pg_stat_progress_vacuum
Next
From: Bharath Rupireddy
Date:
Subject: Re: why pg_walfile_name() cannot be executed during recovery?