| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <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 13:21:47 |
| Message-ID: | 995e06b1-0e50-396e-fce3-934d5e511e27@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-04-07 13:32:42 | Re: why pg_walfile_name() cannot be executed during recovery? |
| Previous Message | Robert Haas | 2022-04-07 13:20:04 | Re: Add index scan progress to pg_stat_progress_vacuum |