Re: Extending range of to_tsvector et al - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Extending range of to_tsvector et al
Date
Msg-id 23937.1349102212@sss.pgh.pa.us
Whole thread Raw
In response to Re: Extending range of to_tsvector et al  (john knightley <john.knightley@gmail.com>)
List pgsql-hackers
john knightley <john.knightley@gmail.com> writes:
> On Mon, Oct 1, 2012 at 11:58 AM, Dan Scott <denials@gmail.com> wrote:
>> So... perhaps LC_CTYPE=C is a possible workaround for you?

> LC_CTYPE would not be a work around - this database needs to be in
> utf8 , the full text search is to be used for a mediawiki.

You're confusing locale and encoding.  They are different things.

> Is this a bug that is being worked on?

No.  As I already tried to explain to you, this behavior is not
determined by Postgres, it's determined by the platform's locale
support.  You need to complain to your OS vendor.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: pg_malloc() versus malloc(0)
Next
From: Peter Geoghegan
Date:
Subject: Re: pg_malloc() versus malloc(0)