Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen? - Mailing list pgsql-admin

From raghu ram
Subject Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
Date
Msg-id CALnrrJTPzsNvaFP_qHisMS=wwp2bkvK=gk_wPDzC-fdaXEkypA@mail.gmail.com
Whole thread Raw
In response to invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?  (Rural Hunter <ruralhunter@gmail.com>)
Responses Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
List pgsql-admin


2012/4/14 Rural Hunter <ruralhunter@gmail.com>
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?


This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".

Try to set client_encoding='LATIN1' 

and then execute 

select to_tsvector(content) from tmp_article;

--

Thanks & Regards,

Raghu Ram

EnterpriseDB: http://www.enterprisedb.com

pgsql-admin by date:

Previous
From: Rural Hunter
Date:
Subject: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
Next
From: Rural Hunter
Date:
Subject: Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?