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

From: "patrick" <patrick(at)11h11(dot)com>
To: "Richard Huxton" <dev(at)archonet(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 15:45:16
Message-ID: 005001c889d8$3aa43380$0d02a8c0@audio
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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

i have only 1 row:
46; "the product name"; "the description";

i don't see any specials chars or accents.

knowing that some of my clients are french, should i use LATIN9 as database
encoding / client encoding? or maybe it's because of the LOCALE
(French/Canada)?

here's the code again:
ALTER TABLE product ADD COLUMN search_vector tsvector;
CREATE INDEX idx_search_vector ON product USING gist(search_vector);
UPDATE product SET search_vector = setweight(to_tsvector(name), 'A') ||
to_tsvector(description);

pat

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Volkan YAZICI 2008-03-19 15:51:50 Re: array_cat without duplicity
Previous Message Martin Gainty 2008-03-19 15:18:38 Re: nntp not workiNG

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-19 16:24:48 Re: Final Thoughts for 8.3 on LWLocking and Scalability
Previous Message Tom Lane 2008-03-19 15:10:26 Re: Multiple SRF right after SELECT