From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>,
        Daniel Verite <daniel@manitou-mail.org>
Subject: Re: psql --help=variables missing csv_fieldsep
In-reply-to: <202511031738.eqaeaedpx5cr@alvherre.pgsql>
References: <202511031738.eqaeaedpx5cr@alvherre.pgsql>
Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
	message dated "Mon, 03 Nov 2025 18:44:31 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <349599.1762193031.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 03 Nov 2025 13:03:51 -0500
Message-ID: <349600.1762193031@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/349600.1762193031%40sss.pgh.pa.us>
Precedence: bulk

=3D?utf-8?Q?=3DC3=3D81lvaro?=3D Herrera <alvherre@kurilemu.de> writes:
> While messing with the \pset boolean display patch, I noticed that psql
> --help=3Dvariables 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_f=
alse|display_true|\n"
...

Some kind of mechanical cross-check does seem like a good idea,
even if it's just a rough one-time effort.

			regards, tom lane