Re: contrib/fulltextindex
От | Oleg Bartunov |
---|---|
Тема | Re: contrib/fulltextindex |
Дата | |
Msg-id | Pine.GSO.4.44.0207221129060.7568-100000@ra.sai.msu.su обсуждение исходный текст |
Ответ на | contrib/fulltextindex ("Tomas Lehuta" <lharp@aurius.sk>) |
Список | pgsql-hackers |
It's known problem with LIKE and non-C locale. You may try contrib/tsearch for full text search. It's works with locale and does index search. Oleg On Mon, 22 Jul 2002, Tomas Lehuta wrote: > Hello! > > i've got a question on my problem.. > i'm using contrib/fulltextindex to index my tables to do a fulltext search > but i'm using a non-default locale settings on my database. > i found out that if the locale is default 'C' then fulltextindex tables are > scanned very fast using btree indices. for sure, i'm using prefix match > (string ~ '^blabla') which is supposed to scan the table in this way.. so > it's ok! > but if i change to different locale (i.e. sk_SK or cs_CZ) the fti table is > scanned sequentially and it's very slow.. so, the more words are there in my > fti table and the more more words i'm trying to search at once using table > join the slower is the search.. > > so my question is.. is this a bug or the prefix match is not supported to > perform a table scan using indices under non-default locale? > please, give me a hint.. > > regards > > Tomas Lehuta > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
В списке pgsql-hackers по дате отправления: