From: Vik Fearing <vik@postgresfriends.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Add \pset options for boolean value display
Date: Sat, 5 Jul 2025 14:41:27 +0200
Message-ID: <30bffc73-2504-49a4-87f2-e3da6776a014@postgresfriends.org> (raw)
In-Reply-To: <1174075.1750804258@sss.pgh.pa.us>
References: <CAKFQuwYts3vnfQ5AoKhEaKMTNMfJ443MW2kFswKwzn7fiofkrw@mail.gmail.com>
<CAKFQuwZaeRT3Nco9sPd-9ZwEuStUZLU+AKH9+iRf4978T59kRg@mail.gmail.com>
<1174075.1750804258@sss.pgh.pa.us>
On 25/06/2025 00:30, Tom Lane wrote:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> On Thu, Mar 20, 2025 at 8:24 PM David G. Johnston <
>> david.g.johnston@gmail.com> wrote:
>>> It's \pset null for boolean values
> Do we really want this?
Yes, many of us do.
> It's the sort of thing that has a strong
> potential to break anything that reads psql output --- and I'd
> urge you to think that human consumers of psql output may well
> be the minority. There's an awful lot of scripts out there.
You mean scripts that don't use --no-psqlrc? Those scripts are already
bug ridden.
--
Vik Fearing
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: vik@postgresfriends.org, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Add \pset options for boolean value display
In-Reply-To: <30bffc73-2504-49a4-87f2-e3da6776a014@postgresfriends.org>
* 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