Re: Document NULL - Mailing list pgsql-hackers

From Marcos Pegoraro
Subject Re: Document NULL
Date
Msg-id CAB-JLwbJz06-H-F2nYBKsGaqNB9aDhT4on-Anhw40Tq-9YoTGg@mail.gmail.com
Whole thread Raw
In response to Re: Document NULL  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Document NULL
List pgsql-hackers
Em qua., 28 de jan. de 2026 às 20:34, David G. Johnston <david.g.johnston@gmail.com> escreveu:
Notably, I went with "Null" as the \pset display null value instead of \N (find-replace and fixes, did not re-run commands in psql, looks correct though and it is fairly mechanical).
It seems you didn't correctly replace \N with Null. 
All nulls inside an array should be uppercase, all are fine.
Json nulls should be lowercase, all are fine
But some nulls of these results have a "null" instead of "Null"
+   country   | flagship
+ id | value | IS NULL | IS DIST | IS !=
+   c   | c IS N | NOT c IS N | c IS NOT N | ROW(v,v) IS N | ROW(v,v) IS NOT N
+ In Present | In Missing | N In Non-N | N In N
+ id | value |  Affirm   |  Negate   | Safe Affirm | Safe Negate
+ id | value | de_id | de_value |   pg_typeof
+ id | IS NULL

Additionally, some column aliases you used NULL, some N and some Null, wouldn't it be better to standardize them ? 
If you agree, would you use uppercase ? I can change them if you want, there are a lot of them.

regards
Marcos

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)
Next
From: Antonin Houska
Date:
Subject: Re: Race conditions in logical decoding