| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(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:37:25 |
| Message-ID: | 3370992.1649349445@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2022-04-07 16:42:36 | Re: How about a psql backslash command to show GUCs? |
| Previous Message | Mark Dilger | 2022-04-07 16:34:47 | Re: How about a psql backslash command to show GUCs? |