From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-06 18:26:36 |
Message-ID: | ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/6/22 13:58, Alvaro Herrera wrote:
> On 2022-Apr-06, Tom Lane wrote:
>
>> However, I very often find myself resorting to the much more tedious
>>
>> select * from pg_settings where name like '%foo%';
>>
>> when I want to see some related parameters, or when I'm a bit
>> fuzzy on the exact name of the parameter.
>
> Been there many times, so +1 for the general idea.
>
>> In the discussion about adding privileges for GUCs [1], there
>> was a proposal to add a new psql backslash command to show GUCs,
>> which could reduce this problem to something like
>>
>> \dcp *foo*
>
> +1. As for command name, I like \show as proposed by Pavel.
+1
I'd love something for the same reasons.
No as sure about \show though. That seems like it could be confused with
showing other stuff. Maybe consistent with \sf[+] and \sv[+] we could
add \sc[+]?
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-06 18:40:40 | Re: How about a psql backslash command to show GUCs? |
Previous Message | Tom Lane | 2022-04-06 18:26:28 | Should pg_dumpall dump ALTER SYSTEM settings? |