| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [v9.2] make_greater_string() does not return a string in some cases |
| Date: | 2011-10-18 04:06:11 |
| Message-ID: | CA+TgmobVjxK6DAuGHJ=nLgnfYHP4s7EAp19E86pzd4DudGhY4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Oct 17, 2011 at 11:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> - Why does the second byte need special handling for 0xED and 0xF4?
>
> http://www.faqs.org/rfcs/rfc3629.html
>
> See section 4 in particular. The underlying requirement is to disallow
> multiple representations of the same Unicode code point.
I'm still confused. The input string is already known to be valid
UTF-8, so the second byte (if there is one) must be between 0x80 and
0xBF. Therefore it will be neither 0xED nor 0xF4.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-18 04:11:38 | Re: [v9.2] make_greater_string() does not return a string in some cases |
| Previous Message | Tom Lane | 2011-10-18 03:54:45 | Re: [v9.2] make_greater_string() does not return a string in some cases |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2011-10-18 04:11:07 | Re: spinlocks on HP-UX |
| Previous Message | Robert Haas | 2011-10-18 04:00:16 | Re: [v9.2] Object access hooks with arguments support (v1) |