From: | Junji TERAMOTO <teramoto(dot)junji(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Hiroshi Saito <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tsearch2 vs core? |
Date: | 2005-07-01 06:00:14 |
Message-ID: | 42C4DBEE.8010603@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello all,
>>tsearch2 now doesn't support multibyte encoding and has problems with UTF :(.
I read this url;
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/donate.shtml
---
- UTF-8 support
Currently, tsearch2's parser doesn't supports utf-8. This is very
important if you want to search multilingual documents.
---
But, there is another document;
"Tsearch2 and Unicode/UTF-8"
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/tsearch2_german_utf8.html
Which is true? The tsearch2 suppoort UTF or not?
If we use "simple" parser, we can store UTF-8 text into tsearch2?
Or, do we have to make own parser which can parse UTF-8 text?
> Japanese Mr. Junji TERAMOTO(NTT) is supporting it.
> http://www.oss.ecl.ntt.co.jp/tsearch2j/
> However, It is EUC_JP. He will probably understand the problem.
> Though I don't understand the problem....
Sorry, I don't understand this problem exactly...
--
Junji Teramoto
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2005-07-01 06:05:44 | Re: Checkpoint cost, looks like it is WAL/CRC |
Previous Message | Michael Fuhr | 2005-07-01 05:08:42 | Re: 3des functions? |