Message-ID: <ae4c3347-d1c7-394f-9a7e-425af6f89a80@joeconway.com>
Date: Wed, 6 Apr 2022 14:26:36 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.7.0
Content-Language: en-US
To: Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org,
 Mark Dilger <mark.dilger@enterprisedb.com>
References: <202204061758.leffczewl4kd@alvherre.pgsql>
From: Joe Conway <mail@joeconway.com>
Subject: Re: How about a psql backslash command to show GUCs?
In-Reply-To: <202204061758.leffczewl4kd@alvherre.pgsql>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/ae4c3347-d1c7-394f-9a7e-425af6f89a80%40joeconway.com>
Precedence: bulk

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