Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: Document NULL
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: 
 <CAKFQuwYBnoOWgA+Zaeiduwb_1fsZ_bECtk8tGqC2NYgPfYhVLQ@mail.gmail.com>
Date: Fri, 30 Jan 2026 11:27:59 +0800
Cc: Marcos Pegoraro <marcos@f10.com.br>,
 =?utf-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>,
 jian he <jian.universality@gmail.com>,
 Jeff Davis <pgsql@j-davis.com>,
 Yugo NAGATA <nagata@sraoss.co.jp>,
 Tom Lane <tgl@sss.pgh.pa.us>,
 Peter Eisentraut <peter@eisentraut.org>,
 David Rowley <dgrowleyml@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DCE7273-CC25-4179-B603-C52C3F906FA5@gmail.com>
References: 
 <CAKFQuwbnFCr+31wpcpzac-uDTCoRSuU6Ka-7YPYw5ZSHR6kqZA@mail.gmail.com>
 <202511111530.xp4avso6b4pb@alvherre.pgsql>
 <CAB-JLwbjzGL-Jtb-AuTrgBkVWKH8LUXDu3wxkLyOLHXUH4UYmg@mail.gmail.com>
 <CAKFQuwaULsfcG=9JmuGO7VXvTOH8hxsuGhwq2zASAYi48SmfRA@mail.gmail.com>
 <CAB-JLwbJz06-H-F2nYBKsGaqNB9aDhT4on-Anhw40Tq-9YoTGg@mail.gmail.com>
 <CAB-JLwYtaKd_QEfw_eV7y33V+C1AzWDW=g=c4THujGi04cF3wg@mail.gmail.com>
 <CAKFQuwYN9rG6uD64BqaVSdv+iL_Nudk7qbQ+Z2reiRa7CaodHQ@mail.gmail.com>
 <CAKFQuwYBnoOWgA+Zaeiduwb_1fsZ_bECtk8tGqC2NYgPfYhVLQ@mail.gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/1DCE7273-CC25-4179-B603-C52C3F906FA5%40gmail.com>
Precedence: bulk


> On Jan 30, 2026, at 10:16, David G. Johnston =
<david.g.johnston@gmail.com> wrote:
>=20
> On Thu, Jan 29, 2026 at 2:18=E2=80=AFPM David G. Johnston =
<david.g.johnston@gmail.com> wrote:
> Thank you for the review.  My bad on these.  I'm working through all =
the examples again to get them cleaned up properly.
>=20
> v11 with the examples work as a separate patch over v10 to be =
squashed.
>=20
> Tried to be consistent on "Title Case" within headers other than a few =
where the all-caps operator really made the most sense.
> Got NULL for SQL null literals throughout and Null for psql display of =
the same.
> Removed abbreviations in titles generally.  Re-worked a couple of the =
more complex ones.
>=20
> Decided to leave my agent instructions in place (xml-styled comment).  =
The flow actually worked pretty well, though it's nuanced enough to be =
wary of false-negatives.  Hopefully I got them all.
>=20
> David J.
>=20
> =
<v11-0002-Update-all-examples.patch><v11-0001-doc-Provide-an-overview-of-N=
ULL-handling.patch>

I failed to build v11:

```
chaol@ChaodeMacBook-Air sgml % make html
/usr/bin/xmllint --nonet --path . --path . --output postgres-full.xml =
--noent --valid postgres.sgml
nullvalues.sgml:735: parser error : StartTag: invalid element name
   s   |  t   | Stored =3D Stored | Stored < Constructor | Stored =3D =
Constructor
                                          ^
nullvalues.sgml:1206: parser error : chunk is not well balanced

^
ddl.sgml:171: parser error : Entity 'nullvalues' failed to parse
 &nullvalues;
             ^
ddl.sgml:5871: parser error : chunk is not well balanced

^
postgres.sgml:105: parser error : Entity 'ddl' failed to parse
  &ddl;
       ^
make: *** [postgres-full.xml] Error 1
```

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/