Re: Add \pset options for boolean value display - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Add \pset options for boolean value display
Date
Msg-id CAKFQuwbNhHz-wcJbFSw19n1n6a-t4PTmFdMM0Yr=MxHchP4Opg@mail.gmail.com
Whole thread Raw
In response to Re: Add \pset options for boolean value display  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
On Monday, November 3, 2025, Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Oct-21, Álvaro Herrera wrote:
> On 2025-Oct-20, David G. Johnston wrote:
> > Thank you.  Seems good from a quick read.  I’m regretting the choice of the
> > display_ prefix; is there any technical limitation or other opposition to
> > using just true and false?
> >
> > \pset true ‘true’
> > \pset false ‘false’

> Uhm.  I don't know.  [...]  I'll gladly take a vote.

I got zero votes and lots of digression, so I have pushed with your
original choice of "display_true" and "display_false".  The "true" and
"false" variable names sound too generic and I think they're more likely
to cause confusion.  I think "null" is not a great name either, but it's
been there since forever so I'm not going to propose changing it.

Thank you.

David J.

pgsql-hackers by date:

Previous
From: "Jelte Fennema-Nio"
Date:
Subject: Re: Bump soft open file limit (RLIMIT_NOFILE) to hard limit on startup
Next
From: Álvaro Herrera
Date:
Subject: psql --help=variables missing csv_fieldsep