Re: preloading indexes - Mailing list pgsql-performance

From Andrew Sullivan
Subject Re: preloading indexes
Date
Msg-id 20041103193528.GB16528@phlogiston.dyndns.org
Whole thread Raw
In response to Re: preloading indexes  (<stuff@opensourceonline.com>)
Responses Re: preloading indexes
Re: preloading indexes
List pgsql-performance
On Wed, Nov 03, 2004 at 12:12:43PM -0700, stuff@opensourceonline.com wrote:
> That's correct - I'd like to be able to keep particular indexes in RAM
> available all the time

If these are queries that run frequently, then the relevant cache
will probably remain populated[1].  If they _don't_ run frequently, why
do you want to force the memory to be used to optimise something that
is uncommon?  But in any case, there's no mechanism to do this.

A

[1] there are in fact limits on the caching: if your data set is
larger than memory, for instance, there's no way it will all stay
cached.  Also, VACUUM does nasty things to the cache.  It is hoped
that nastiness is fixed in 8.0.

--
Andrew Sullivan  | ajs@crankycanuck.ca
The plural of anecdote is not data.
        --Roger Brinner

pgsql-performance by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Restricting Postgres
Next
From: Pierre-Frédéric Caillaud
Date:
Subject: Re: preloading indexes