| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, Mario Weilguni *EXTERN* <mweilguni(at)sime(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-03-13 15:38:01 |
| Message-ID: | 45F6C559.7060909@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Albe Laurenz wrote:
>> A fix could be either that the server checks escape sequences for
>> validity
>>
>
> This strikes me as essential. If the db has a certain encoding ISTM we
> are promising that all the text data is valid for that encoding.
>
> The question in my mind is how we help people to recover from the fact
> that we haven't done that.
Is this any different than the issues of moving 8.0.x to 8.1 UTF8? Where
we had to use iconv?
Joshua D. Drake
>
> cheers
>
> andrew
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario Weilguni | 2007-03-13 15:42:35 | Re: Bug in UTF8-Validation Code? |
| Previous Message | Andrew Dunstan | 2007-03-13 15:12:33 | Re: Bug in UTF8-Validation Code? |