Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3

From: Richard Huxton <dev(at)archonet(dot)com>
To: patrick <patrick(at)11h11(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3
Date: 2008-03-19 08:56:54
Message-ID: 47E0D556.8030906@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

patrick wrote:
> hi,
>
> i have an issue with tseach2, i just installed postgresql 8.3.1 on
> windows using UTF8 server encoding / client encoding and LOCALE Canada /
> French.

> UPDATE product SET search_vector = setweight(to_tsvector(name), 'A') ||
> to_tsvector(description);
>
> ERROR: invalid byte sequence for encoding "UTF8": 0xc3
> SQL state: 22021
> Hint: This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is controlled by "client_encoding".

Can you identify which row(s) are causing this problem? If we have the
value that's causing this, someone can reproduce it.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Arturo Pérez 2008-03-19 11:52:36 nntp not workiNG
Previous Message Alban Hertroys 2008-03-19 05:40:16 Re: Problem with async notifications of table updates

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2008-03-19 09:51:12 Re: [PATCHES] Fix for large file support (nonsegment mode support)
Previous Message Peter Eisentraut 2008-03-19 08:38:12 Re: [PATCHES] Fix for large file support (nonsegment mode support)