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

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-04-07 01:27:23
Message-ID: 6693b128-b9e5-fd5e-e8d2-b331dac52cb8@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/6/22 9:18 PM, David G. Johnston wrote:
> On Wed, Apr 6, 2022 at 6:16 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us

> 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

+1 for \dconf

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2022-04-07 01:32:31 Re: Last day of commitfest
Previous Message David G. Johnston 2022-04-07 01:18:33 Re: How about a psql backslash command to show GUCs?