Re: Bug in UTF8-Validation Code?

Andrew - Supernews <andrew+nonews@supernews.com>

From: Andrew - Supernews <andrew+nonews@supernews.com>
To: pgsql-hackers@postgresql.org
Date: 2007-04-03T00:58:32Z
Lists: pgsql-hackers
On 2007-04-02, Mark Dilger <pgsql@markdilger.com> wrote:
> Here's the code for the new chr() function:
>
>      if (pg_database_encoding_max_length() > 1 && !lc_ctype_is_c())

Clearly wrong - this allows returning invalid UTF8 data in locale C, which
is not an uncommon setting to use.

Treating the parameter as bytes is wrong too - it should correspond to
whatever the natural character numbering for the encoding is; for utf8
that is the Unicode code point.

-- 
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services