| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add \pset options for boolean value display |
| Date: | 2025-10-20 20:51:37 |
| Message-ID: | CAKFQuwYWdocoCsfDOZhY2xALM1U89O4bP=Ou266pAOdVojgpfw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, October 20, 2025, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2025-Jun-24, David G. Johnston wrote:
>
> > v1, Ready aside from bike-shedding the name.
>
> Here's v2 after some kibitzing. What do you think?
>
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)’
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-10-20 20:52:16 | Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() |
| Previous Message | Dimitrios Apostolou | 2025-10-20 20:50:44 | Re: [PING] [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward |