Re: Add \pset options for boolean value display

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add \pset options for boolean value display
Date: 2025-10-21 02:51:28
Message-ID: 5BA8FA39-818E-4F95-A9F5-2A3FED0A5732@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Oct 21, 2025, at 10:29, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> They could probably modify their own query to do that if they really wanted to fool someone and I’m having trouble accepting this happening by accident.

If they modify queries, the result can visibly correlate to the query, for example:

```
evantest=# select CASE WHEN TRUE THEN 'f' END as t;
t
---
f
(1 row)
```

There is no confusion. But if a user did some test by setting “display_true = f” previous and forget about it, there is a no any indication in current SQL statement but unexpected results might be shown.

> Do we test for yes/no; oui/non (i.e., foreign language choices); checkmark/X?
>

When I said “basic sanity check”, I only meant something like “display_true” cannot be “false” and “f”.

I won’t argue more. It’s also reasonable to let users take own responsibilities to stay away from wrong behavior.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-10-21 02:55:43 Re: BRIN: Prevent the heapblk overflow during index summarization on very large tables resulting in an infinite loop
Previous Message David G. Johnston 2025-10-21 02:48:04 Re: Add \pset options for boolean value display