Downloads
Home   >   mailing lists

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 CAKFQuwZQUCiCc3c1JESS=q33maA2y_A4K-ZyZ1u_v8EnEG869Q@mail.gmail.com
Whole thread Raw
In response to Re: Add \pset options for boolean value display  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-hackers
Tree view
On Wed, Jun 25, 2025 at 11:03 AM Daniel Verite <daniel@manitou-mail.org> wrote:
        David G. Johnston wrote:

> > It's \pset null for boolean values
> >
>
> v1, Ready aside from bike-shedding the name.

An annoying weakness of this approach is that it cannot detect
booleans inside arrays or composite types

Arrays are probably doable.  The low volume of composite literal outputs is not worth worrying about.
 
or COPY output,
meaning that the translation of t/f is incomplete.

pset doesn't affect COPY output ever so this doesn't seem problematic.


Also it reminds of a previous discussion (see [1]) where pretty much
the same idea was proposed (and eventually rejected at the time).


[1] https://postgr.es/m/56308F56.8060908%40joh.to


Ok, so yes, I really want this hack in psql.  It fits with pset formats and affects our \d and other table-producing meta-commands.  Plus I'd like to use it for documentation examples.

Maybe that's enough to change some decade-old opinions.  Mine's apparently changed since then.

David J.


 

pgsql-hackers by date:

Previous
From: Alexander Pyhalov
Date:
Subject: Re: SCRAM pass-through authentication for postgres_fdw
Next
From: "David G. Johnston"
Date:
Subject: Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close