From: Tom Lane <tgl@sss.pgh.pa.us>
To: listeria@disroot.org
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Section 4.1.2.3 repeats information presented in section 4.1.1
In-reply-to: 
 <170232539471.398198.13861151281926916858@wrigleys.postgresql.org>
References: <170232539471.398198.13861151281926916858@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Mon, 11 Dec 2023 20:09:54 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2445457.1702398326.1@sss.pgh.pa.us>
Date: Tue, 12 Dec 2023 11:25:26 -0500
Message-ID: <2445458.1702398326@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2445458.1702398326%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> The following documentation comment has been logged on the website:
> Page: https://www.postgresql.org/docs/16/sql-syntax-lexical.html
> Description:

> it just threw me off to read the exact same thing twice in quick succession,
> I'd suggest linking to section 4.1.2.3 in section 4.1.1 instead.

They are *not* the same.  The quoting is different and the
meaning is quite different, just as "slon" and 'slon' are
not equivalent in SQL.  Moreover, there's little reason to
assume that somebody coming to 4.1.2.3 necessarily just
read 4.1.1.

Perhaps it'd be better to use different example strings though?

			regards, tom lane