From: Tom Lane <tgl@sss.pgh.pa.us>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Daniel Verite <daniel@manitou-mail.org>
Subject: Re: psql --help=variables missing csv_fieldsep
Date: Mon, 03 Nov 2025 15:53:29 -0500
Message-ID: <374722.1762203209@sss.pgh.pa.us> (raw)
In-Reply-To: <202511032011.xiybfttm3rwc@alvherre.pgsql>
References: <202511032011.xiybfttm3rwc@alvherre.pgsql>
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@kurilemu.de, pgsql-hackers@lists.postgresql.org, daniel@manitou-mail.org
Subject: Re: psql --help=variables missing csv_fieldsep
In-Reply-To: <374722.1762203209@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox