From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Abbath <abbath(at)invitel(dot)hu> |
Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: tsearch is slow |
Date: | 2006-03-15 19:49:00 |
Message-ID: | 1142452140.20149.39.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
> > 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
From | Date | Subject | |
---|---|---|---|
Next Message | Moises Alberto Lindo Gutarra | 2006-03-15 22:06:28 | Re: PostgreSQL Free Visual Manager |
Previous Message | Abbath | 2006-03-15 19:36:09 | Re: tsearch is slow |