Re: Document NULL

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Document NULL
Date: 2024-12-23 21:17:44
Message-ID: CAKFQuwaL+XKvyKvRXeB6G1DMjtxUGveMRiRpna35UHyT+f8KNg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 23, 2024 at 11:39 AM Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:

> Em dom., 22 de dez. de 2024 às 15:07, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
>
> On section Null-Valued Settings is not easy to understand that "show
> example.string" will result in an "ERROR: unrecognized...", that BEGIN or
> ROLLBACK does not return anything. So, what do you think about creating a
> table with two columns and showing command and result side by side ?
>
>
I think I'll replace the use of SHOW with current_setting throughout the
entire example. That should increase the clarity and lets me return
true/false with the column indicating the test - like the existing use of
current_setting does.

David J.

p.s.
I really wish someone had gotten around to implementing \pset true 'true'
and \pset false 'false' ... however we ended up with boolean outputs being
"f" and "t" a bunch of people must have chosen to invest their life savings
in eyewear companies.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2024-12-23 21:31:32 stored procedures vs pg_stat_statements
Previous Message Peter Geoghegan 2024-12-23 20:47:35 Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID