From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: preloading indexes
Date: Wed, 3 Nov 2004 14:35:28 -0500
Message-ID: <20041103193528.GB16528@phlogiston.dyndns.org> (raw)
In-Reply-To: <20041103191247.GFZT27576.fed1rmmtao07.cox.net@CYGNUS>
References: <004b01c4c1ce$cd969c80$8300a8c0@solent>
<20041103191247.GFZT27576.fed1rmmtao07.cox.net@CYGNUS>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: preloading indexes
In-Reply-To: <20041103193528.GB16528@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox