Skip site navigation (1) Skip section navigation (2)

Re: default_text_search_config

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: default_text_search_config
Date: 2007-10-05 07:40:25
Message-ID: 20071005162025.D6A3.ITAGAKI.TAKAHIRO@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:

> You know that PostgreSQL allows only one locale for a PostgreSQL
> cluster, and the fact that text-search being depending on locale
> prevent it from processing multi language text.
>
> The only solution I can think of today is creating new parser which
> can process EUC_JP properly (I mean it can process not only Japanese
> but also English) and use it on C locale/EUC_JP cluster. I would do
> this for 8.4 if I have time.

The correct solution is probably we will have multiple locales in
single database cluster. We should set the locale after deciding
the encoding nowm, but I think the current implementation is wrong
because locale depends on encoding, but the opposite is not true.
(locale = 'language_country.*encoding*')

If you will go to the multiple text-search support, we'd better to
get done the locale issue first. It might affect your new parser.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center



In response to

Responses

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2007-10-05 08:21:03
Subject: Re: default_text_search_config
Previous:From: Tatsuo IshiiDate: 2007-10-05 07:12:58
Subject: Re: default_text_search_config

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group