Message-ID: <4F8BDDB2.9020801@gmail.com>
Date: Mon, 16 Apr 2012 16:52:02 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: invalid byte sequence for encoding "UTF8": 0xf481 - how
	could this happen?
References: <4F88DB40.9070609@gmail.com>
	<D960CB61B694CF459DCFB4B0128514C207BB6CE6@exadv11.host.magwien.gv.at>
In-Reply-To: 
 <D960CB61B694CF459DCFB4B0128514C207BB6CE6@exadv11.host.magwien.gv.at>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

=>SELECT convert_to(content, 'UTF8') FROM tmp_article;
This works. My pg is at latest 9.1.3 on ubuntu 10.04 server. We have 
millions of data in the db but this is the only one we met the problem. 
The bad data is inserted in recent days and we upgraded to 9.1.3 right 
after it was released.

于 2012/4/16 16:31, Albe Laurenz 写道:
> Rural Hunter wrote:
>> My db is in utf-8, I have a row in my table say tmp_article and I
> wanted
>> to generate ts_vector from the article content:
>> select to_tsvector(content) from tmp_article;
>> But I got this error:
>> ERROR:  invalid byte sequence for encoding "UTF8": 0xf481
>>
>> I am wondering how this could happen. I think if there was invalid
> UTF8
>> bytes in the content, it shouldn't have been able to inserted into the
>> tmp_article table as I sometimes see similar errors when inserting
>> records to tmp_article. Am I right?
> You are right in theory.  A lot depends on your PostgreSQL version,
> because
> the efforts to prevent invalid strings from entering the database have
> led to changes over the versions.  Older versions are more permissive.
>
> To test the theory that the contents of the table are bad, you can
> test if the same happens if you
>
> SELECT convert_to(content, 'UTF8') FROM tmp_article;
>
> Yours,
> Laurenz Albe
>