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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: patrick <patrick(at)11h11(dot)com>, 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 19:44:30
Message-ID: 18872.1205955870@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Richard Huxton <dev(at)archonet(dot)com> writes:
> The issue is what characters were in your script file.

I'm wondering about non-UTF8 characters in the dictionary file(s) used
by the text search configuration. Failure to load a configuration
file would explain why it only shows up in tsearch-related queries.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message patrick 2008-03-19 20:11:22 Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3
Previous Message Leon Mergen 2008-03-19 19:39:54 Foreign keys to inherited tables

Browse pgsql-hackers by date

  From Date Subject
Next Message patrick 2008-03-19 20:11:22 Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3
Previous Message Richard Huxton 2008-03-19 19:16:36 Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3