Re: Bug in UTF8-Validation Code? - Mailing list pgsql-hackers

From Andrew - Supernews
Subject Re: Bug in UTF8-Validation Code?
Date
Msg-id slrnf139lo.2i67.andrew+nonews@atlantis.supernews.net
Whole thread Raw
In response to Bug in UTF8-Validation Code?  (Mario Weilguni <mweilguni@sime.com>)
List 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


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Re: CheckpointStartLock starvation
Next
From: Bruce Momjian
Date:
Subject: Re: Modifying TOAST thresholds