Tatsuo Ishii <ishii@postgresql.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
