| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | john knightley <john(dot)knightley(at)gmail(dot)com> |
| Cc: | Dan Scott <denials(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Extending range of to_tsvector et al |
| Date: | 2012-10-01 14:36:52 |
| Message-ID: | 23937.1349102212@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
john knightley <john(dot)knightley(at)gmail(dot)com> writes:
> On Mon, Oct 1, 2012 at 11:58 AM, Dan Scott <denials(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2012-10-01 14:37:11 | Re: pg_malloc() versus malloc(0) |
| Previous Message | Dimitri Fontaine | 2012-10-01 14:30:01 | Re: pg_malloc() versus malloc(0) |