Re: Add \pset options for boolean value display

Daniel Verite <daniel@manitou-mail.org>

From: "Daniel Verite" <daniel@manitou-mail.org>

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

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

Date: 2025-06-25T18:03:01Z

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

	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 or COPY output,
meaning that the translation of t/f is incomplete.

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

Best regards,
-- 
Daniel Vérité 
https://postgresql.verite.pro/