| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | 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 03:25:06 |
| Message-ID: | CAApHDvoCyxBZqdvwc93cnsr_48zBY7wwYmZHhCjhgp-naiDKSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2022-04-07 03:45:56 | Re: Window Function "Run Conditions" |
| Previous Message | wangw.fnst@fujitsu.com | 2022-04-07 03:08:14 | RE: Data is copied twice when specifying both child and parent table in publication |