| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Subject: | Re: psql --help=variables missing csv_fieldsep |
| Date: | 2025-11-03 20:53:29 |
| Message-ID: | 374722.1762203209@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> On 2025-Nov-03, Tom Lane wrote:
>> But wait ... is it actually a variable? help.c does list it, but
>> as a \pset option:
> Yeah, there are two lists: one here in the "\?" output, and another in
> the "\? variables" output, which is also `psql --help=variables`. It
> lists actual variables but also \pset options and environment variables
> psql recognizes.
Huh. I would not have called \pset options variables, but I guess
somebody thought it made sense.
> I find this one you quote somewhat unreadable, so I
> was going to propose to remove it, and instead direct the user to look
> at "\? variables" for the exhaustive list. That one is also a bit
> easier to cross-check, I think. (There's also tab-complete.)
Agreed that the set of \pset options has bloated to the point where
that presentation is unreadable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-11-03 21:27:59 | Re: Resetting recovery target parameters in pg_createsubscriber |
| Previous Message | Mihail Nikalayeu | 2025-11-03 20:41:00 | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |