contrib/fulltextindex

From: "Tomas Lehuta" <lharp(at)aurius(dot)sk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: contrib/fulltextindex
Date: 2002-07-19 13:14:15
Message-ID: ah93b3$1phl$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 has no support to
perform a table scan using indices under non-default locale?
please, give me a hint..

regards

Tomas Lehuta

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2002-07-19 14:11:05 Re: RFC: listing lock status
Previous Message Christopher Kings-Lynne 2002-07-19 08:50:24 Demo patch for DROP COLUMN