From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: rsindlin@gmail.com
Subject: Misleading "For more information..." placement
Date: Sat, 25 Mar 2023 15:43:56 +0000
Message-ID: <167975903644.3349096.5840068880132333322@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/datatype-character.html
Description:
In the paragraph
> The characters that can be stored in any of these data types are
determined by the database character set, which is selected when the
database is
> created. Regardless of the specific character set, the character with code
zero (sometimes called NUL) cannot be stored. For more information refer to
Section 24.3.
The final sentence ("For more information refer to Section 24.3") is easily
read to refer to more information being available about character code zero
(NUL). However, section 24.3 has no mention of NUL, but rather the
available database character sets. I'd suggest moving that last sentence to
immediately after the first sentence, which ends with "...when the database
is created."
A really minor point, but it caught me off-guard.
Best,
-Randall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, rsindlin@gmail.com
Subject: Re: Misleading "For more information..." placement
In-Reply-To: <167975903644.3349096.5840068880132333322@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox