| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add \pset options for boolean value display |
| Date: | 2025-07-05 12:41:27 |
| Message-ID: | 30bffc73-2504-49a4-87f2-e3da6776a014@postgresfriends.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25/06/2025 00:30, Tom Lane wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> On Thu, Mar 20, 2025 at 8:24 PM David G. Johnston <
>> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>>> It's \pset null for boolean values
> Do we really want this?
Yes, many of us do.
> It's the sort of thing that has a strong
> potential to break anything that reads psql output --- and I'd
> urge you to think that human consumers of psql output may well
> be the minority. There's an awful lot of scripts out there.
You mean scripts that don't use --no-psqlrc? Those scripts are already
bug ridden.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-07-05 14:01:52 | Re: Inconsistent LSN format in pg_waldump output |
| Previous Message | Dilip Kumar | 2025-07-05 11:21:34 | Re: Conflict detection for update_deleted in logical replication |