Postgres Pro
Downloads
Home   >   mailing lists

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 CALnrrJSCuGpJTRx_Vg8efcs+o-t0=PABpcOz5AJ+jkZ=jTNq+g@mail.gmail.com
Whole thread Raw
In response to Re: 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?  (Rural Hunter <ruralhunter@gmail.com>)
List pgsql-admin
Tree view


On Sat, Apr 14, 2012 at 9:31 AM, Rural Hunter <ruralhunter@gmail.com> wrote:
doesn't work either.

db=# show client_encoding;
 client_encoding
-----------------
 UTF8
(1 row)

db=# set client_encoding='LATIN1';
SET
db=# show client_encoding;
 client_encoding
-----------------
 LATIN1
(1 row)

db=# select to_tsvector(content) from tmp_article;

ERROR:  invalid byte sequence for encoding "UTF8": 0xf481

Try to set client_encoding='SQL_ASCII' 

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: Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
Next
From: Wells Oliver
Date:
Subject: Trouble w/ COPY command