Re: tsearch is slow

Hello Scott,

Wednesday, March 15, 2006, 8:49:00 PM, you wrote:

> On Wed, 2006-03-15 at 13:36, Abbath wrote:
>> Hello Richard,
>>
>> Wednesday, March 15, 2006, 3:35:26 PM, you wrote:
>> > If you want to force the data to be cached, just put a cron-job in to
>> > run a query for "abc" or whatever once a minute.
>>
>> I can't guess what the user want to search.

> But that query will likely load up all the index info into memory.

Misunderstanding: I experienced that if I run a search for a keyword
first time it is slow, then next time it is fast BUT for that keyword,
not for any keyword.

>> > Of course, if it turns out that your users aren't running the query very
>> > often then you're wasting resources, and if they are running it often
>> > then again you're wasting resources. But - if you really need to, that's
>> > the solution.
>>
>> It seems if I periodically use VACUUM ANALYZE, it helps to reduce the search
>> time...I will see how can I tune it more.

> That statement is pretty telling. You're new to PostgreSQL I'll
> assume. You'll need to read up on the periodic maintenance section of
> the docs.

> Here ya go:
> http://www.postgresql.org/docs/8.1/interactive/maintenance.html

Yes, I have just started to use postgres so I need further experience.
Thanks for the link.

> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly