Horton
Menu

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

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Joe Conway <mail@joeconway.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Mark Dilger <mark.dilger@enterprisedb.com>
Date: 2022-04-07T01:18:33Z
Lists: pgsql-hackers 
On Wed, Apr 6, 2022 at 6:16 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
> > I am a bit torn between "\dcp" (or \dsetting / \dconfig? we don't
> > necessarily need for it to be super short) and "\sc". Certainly with
> > pattern matching the interface for the "\d" commands would fit that
> > pattern. "\sc" would make sense for a thorough introspection of what is
> > in the GUC. That said, we get that with SHOW today.
>
> > So I'm leaning towards something in the "\d" family.
>
> I agree that \d-something makes the most sense from a functionality
> standpoint.  But I don't want to make the name too long, even if we
> do have tab completion to help.
>
> \dconf maybe?
>
>
I don't have a strong preference, but just tossing it out there; maybe
embrace the novelty of GUC?

\dguc

David J.

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.