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

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-04-07 16:58:43
Message-ID: 711e43b9-6499-6a8b-0802-fb549874658e@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/7/22 12:37, Tom Lane wrote:
> Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> writes:
>>> On Apr 7, 2022, at 9:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 going to 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2022-04-07 17:04:19 Re: How about a psql backslash command to show GUCs?
Previous Message Andres Freund 2022-04-07 16:57:09 Re: test/isolation/expected/stats_1.out broken for me