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

From: raghu ram <raghuchennuru(at)gmail(dot)com>
To: Rural Hunter <ruralhunter(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
Date: 2012-04-14 17:38:54
Message-ID: CALnrrJSCuGpJTRx_Vg8efcs+o-t0=PABpcOz5AJ+jkZ=jTNq+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Sat, Apr 14, 2012 at 9:31 AM, Rural Hunter <ruralhunter(at)gmail(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2012-04-14 22:45:47 Trouble w/ COPY command
Previous Message Rural Hunter 2012-04-14 04:01:08 Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?