Horton

Re: Bug in UTF8-Validation Code?

Mario Weilguni <mweilguni@sime.com>

View thread View on postgr.es
From: Mario Weilguni <mweilguni@sime.com>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Albe Laurenz <all@adv.magwien.gv.at>, pgsql-hackers@postgresql.org
Date: 2007-03-13T15:42:35Z
Lists: pgsql-hackers 
Am Dienstag, 13. März 2007 16:38 schrieb Joshua D. Drake:
> 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?
>

What issues? I've upgraded several 8.0 database to 8.1. without having to use 
iconv. Did I miss something?

Regards,
Mario Weilguni