From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | ishii(at)sraoss(dot)co(dot)jp, grzm(at)seespotcode(dot)net, teodor(at)sigaev(dot)ru, bruce(at)momjian(dot)us, hannu(at)skype(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tsearch in core patch |
Date: | 2007-06-25 03:19:06 |
Message-ID: | 20070625.121906.59655339.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I would be surprised if C locale defaulted to anything except English.
Don't be surprised. The mechanism of collation is too simple for
Japanse Kanji, and locale is not usefull for Japanse anyway. That's
why Japanese installations of PostgreSQL tend to use C locale.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
> I suppose it would be sensible to add a switch to allow people to select
> a different language. In any case, the only thing initdb would be doing
> would be setting up an initial value of a table entry or GUC variable,
> so you could always change it yourself later; it may not be worth
> sweating too much about this.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-25 04:10:03 | Re: Server-side support of all encodings |
Previous Message | Tatsuo Ishii | 2007-06-25 03:16:23 | Re: [Fwd: Re: tsearch in core patch] |