Horton
Menu

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

Joe Conway <mail@joeconway.com>

View thread
From: Joe Conway <mail@joeconway.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Mark Dilger <mark.dilger@enterprisedb.com>
Date: 2022-04-07T12:36:28Z
Lists: pgsql-hackers 
On 4/6/22 23:02, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
>> +1 for \dconf
> 
> Here's a draft patch using \dconf.  No tests or docs yet.

WFM -- using some form of \d<something> makes more sense than 
\s<something>, and I can't think of anything better that \dconf.

I will say that I care about context far more often than unit or type 
though, so from my point of view I would switch them around with respect 
to which is only shown with verbose.

Joe

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.