Re: psql --help=variables missing csv_fieldsep

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:20:28
Message-ID: 202511032011.xiybfttm3rwc@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Nov-03, Tom Lane wrote:

> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> > While messing with the \pset boolean display patch, I noticed that psql
> > --help=variables is missing csv_fieldsep. Is there a reason for this?
>
> But wait ... is it actually a variable? help.c does list it, but
> as a \pset option:
>
> HELP0(" \\pset [NAME [VALUE]] set table output option\n"
> " (border|columns|csv_fieldsep|display_false|display_true|\n"

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. 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.)

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"No renuncies a nada. No te aferres a nada."

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mats Kindahl 2025-11-03 20:20:32 Re: Use stack-allocated StringInfoData
Previous Message Melanie Plageman 2025-11-03 20:06:54 Re: Eagerly evict bulkwrite strategy ring