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

2008-03-20 Thread Tom Lane
Martijn van Oosterhout <[EMAIL PROTECTED]> writes: > On Wed, Mar 19, 2008 at 07:55:40PM -0400, Tom Lane wrote: >> (that's \303\240 or 0xc3 0xa0). I am thinking that something decided >> the \240 was junk and removed it. > Hmm, it is coincidently the space character +0x80, which is defined as > a

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

2008-03-20 Thread Martijn van Oosterhout
On Wed, Mar 19, 2008 at 07:55:40PM -0400, Tom Lane wrote: > (that's \303\240 or 0xc3 0xa0). I am thinking that something decided > the \240 was junk and removed it. Hmm, it is coincidently the space character +0x80, which is defined as a non-breaking space in many Latin encodings. Perhaps ctype d

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

2008-03-19 Thread Tom Lane
Richard Huxton <[EMAIL PROTECTED]> writes: > Missed the mailing list on the last reply >> patrick wrote: >>> thoses queries are not working, same message: >>> ERROR: invalid byte sequence for encoding "UTF8": 0xc3 >>> >>> what i found is in postgresql.conf if i change: >>> default_text_search_confi