Message-ID: <efcd5fee059c8868ca47525a8cfdc8f42cf95fdc.camel@j-davis.com>
Subject: Re: Inaccurate documentation about identifiers
From: Jeff Davis <pgsql@j-davis.com>
To: Brennan Vincent <brennan@umanwizard.com>, pgsql-bugs@lists.postgresql.org
Date: Thu, 17 Nov 2022 11:12:39 -0800
In-Reply-To: <feb15ca0-f449-c862-9414-66220e80304d@umanwizard.com>
References: <feb15ca0-f449-c862-9414-66220e80304d@umanwizard.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu1 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/efcd5fee059c8868ca47525a8cfdc8f42cf95fdc.camel%40j-davis.com>
Precedence: bulk

On Wed, 2022-11-16 at 08:36 -0500, Brennan Vincent wrote:
> Hello,
>=20
> The documentation states:
>=20
> "SQL identifiers and key words must begin with a letter (a-z, but
> also letters
> with diacritical marks and non-Latin letters) or an underscore (_).
> Subsequent
> characters in an identifier or key word can be letters, underscores,
> digits
> (0-9), or dollar signs ($)"
>=20
> However, it seems that all non-ASCII characters are considered
> "letters"

You're correct: it seems to allow any byte with the high bit set;
including, for example, a zero-width space.

I don't think we want to change the documentation here, because that
would amount to a promise that we support such identifiers forever.

I also don't think we want to change the code, because it opens up
several problems and I'm not sure it's worth trying to solve them.

Is there any harm just leaving it as-is?


--=20
Jeff Davis
PostgreSQL Contributor Team - AWS