Re: Document NULL - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Document NULL
Date
Msg-id CAKFQuwaL+XKvyKvRXeB6G1DMjtxUGveMRiRpna35UHyT+f8KNg@mail.gmail.com
Whole thread Raw
In response to Re: Document NULL  (Marcos Pegoraro <marcos@f10.com.br>)
List pgsql-hackers
On Mon, Dec 23, 2024 at 11:39 AM Marcos Pegoraro <marcos@f10.com.br> wrote:
Em dom., 22 de dez. de 2024 às 15:07, David G. Johnston <david.g.johnston@gmail.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.


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID
Next
From: Merlin Moncure
Date:
Subject: stored procedures vs pg_stat_statements