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

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Huxton <dev(at)archonet(dot)com>, patrick <patrick(at)11h11(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, PG-General Mailing List <pgsql-general(at)postgreSQL(dot)org>
Subject: Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3
Date: 2008-03-20 13:16:04
Message-ID: 20080320131604.GC12266@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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 decided it
was a space, or sscanf didn't read it...

Have anice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chetan Bob 2008-03-20 13:22:49 How can i connect my application dynamically to postgres schema.
Previous Message Martijn van Oosterhout 2008-03-20 13:08:13 Re: Problem with async notifications of table updates

Browse pgsql-hackers by date

  From Date Subject
Next Message NikhilS 2008-03-20 13:25:43 Re: Problem identifying constraints which should not be inherited
Previous Message Alvaro Herrera 2008-03-20 12:41:17 Re: Problem identifying constraints which should not be inherited