Re: tsearch2, large data and indexes - Mailing list pgsql-performance

From Ivan Voras
Subject Re: tsearch2, large data and indexes
Date
Msg-id CAF-QHFWNt-+AKyYQDf=d56b198tRObmfrNwzBj78h2CLUw3T4g@mail.gmail.com
Whole thread Raw
In response to Re: tsearch2, large data and indexes  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: tsearch2, large data and indexes  (Sergey Konoplev <gray.ru@gmail.com>)
List pgsql-performance
On 24 April 2014 13:34, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:

> As the docs say, the GIN index does not store the weights. As such, there is
> no need to strip them. A recheck would be necessary if your query needs the
> weights, precisely because the weights are not included in the index.
>
> (In the OP's query, it's the ranking that was causing the detoasting.)

Thanks!

My problem is that I actually need the ranking. My queries can return
a large number of documents (tens of thousands) but I usually need
only the first couple of pages of most relevant results (e.g. 50-100
records). With PostgreSQL and tsearch2, this means that the tens of
thousands of documents found via the index are then detoasted and
ranked.

Does anyone have experience with external search engines which also
have ranking but are more efficient? How about Solr?


pgsql-performance by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: tsearch2, large data and indexes
Next
From: Sergey Konoplev
Date:
Subject: Re: tsearch2, large data and indexes