Re: Add \pset options for boolean value display

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>

To: "David G. Johnston" <david.g.johnston@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-10-20T21:08:21Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add \pset options for boolean value display
- 645cb44c5490 19 (unreleased) landed

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’
> 
> To keep in line with:
> 
> \pset null ‘(null)’

Uhm.  I don't know.  No technical limitation AFAICS.  It looks a bit
weird to me, because those names are so generic; but also I cannot
really object to them.  That said, such a last-minute bikeshed comment
seems like a perfect way to kill your patch.

I'll gladly take a vote.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X  - http://www.thelinuxreview.com/TUX/)