Horton
Menu

Re: How about a psql backslash command to show GUCs?

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, Mark Dilger <mark.dilger@enterprisedb.com>
Date: 2022-04-06T17:58:02Z
Lists: pgsql-hackers 
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.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Be more careful about GucSource for internally-driven GUC settings.

  2. Fix case sensitivity in psql's tab completion for GUC names.

  3. Further tweak the default behavior of psql's \dconfig.

  4. Tweak the default behavior of psql's \dconfig.

  5. psql: add \dconfig command to show server's configuration parameters.

  6. Allow granting SET and ALTER SYSTEM privileges on GUC parameters.