Horton
Menu

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

Vik Fearing <vik@postgresfriends.org>

View thread
From: Vik Fearing <vik@postgresfriends.org>
To: Tom Lane <tgl@sss.pgh.pa.us>, Christoph Berg <myon@debian.org>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, Joe Conway <mail@joeconway.com>, Mark Dilger <mark.dilger@enterprisedb.com>, Andrew Dunstan <andrew@dunslane.net>, David Rowley <dgrowleyml@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-04-09T16:50:52Z
Lists: pgsql-hackers 
On 4/9/22 16:31, Tom Lane wrote:
> Christoph Berg <myon@debian.org> writes:
>
>> I would think that if \dconfig showed the non-default settings only,
>> it would be much more useful; the full list would still be available
>> with "\dconfig *". This is in line with \dt only showing tables on the
>> search_path, and "\dt *.*" showing all.
> 
> Hm, I could get on board with that -- any other opinions?

+1
-- 
Vik Fearing

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.