Re: How about a psql backslash command to show GUCs? - Mailing list pgsql-hackers

From Joe Conway
Subject Re: How about a psql backslash command to show GUCs?
Date
Msg-id 711e43b9-6499-6a8b-0802-fb549874658e@joeconway.com
Whole thread Raw
In response to Re: How about a psql backslash command to show GUCs?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: How about a psql backslash command to show GUCs?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On 4/7/22 12:37, Tom Lane wrote:
> Mark Dilger <mark.dilger@enterprisedb.com> writes:
>>> On Apr 7, 2022, at 9:29 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> I wouldn't
>>> fight too hard if people want to lengthen it to \dconfig for consistency
>>> with set_config().
> 
>> I'd prefer \dconfig, but if the majority on this list view that as pedantically forcing them to type more, I'm not
goingto kick up a fuss about \dconf.
 
> 
> Maybe I'm atypical, but I'm probably going to use tab completion
> either way, so it's not really more keystrokes.  The consistency
> point is a good one that I'd not considered before.

Yeah I had thought about \dconfig too -- +1 to that, although I am fine 
with \dconf too.

Joe



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: test/isolation/expected/stats_1.out broken for me
Next
From: "David G. Johnston"
Date:
Subject: Re: How about a psql backslash command to show GUCs?