pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: pgsql-performance@postgresql.org
Subject: Re: preloading indexes
Date: Wed, 03 Nov 2004 20:50:04 +0100
Message-ID: <opsgwmpq0fcq72hf@musicbox> (raw)
In-Reply-To: <20041103193528.GB16528@phlogiston.dyndns.org>
References: <004b01c4c1ce$cd969c80$8300a8c0@solent>
	<20041103191247.GFZT27576.fed1rmmtao07.cox.net@CYGNUS>
	<20041103193528.GB16528@phlogiston.dyndns.org>


	--

	uh, you can always load a table in cache by doing a seq scan on it...  
like select count(1) from table or something... this doesn't work for  
indexes of course, but you can always look in the system catalogs, find  
the filename for the index, then just open() it from an external program  
and read it without caring for the data... it'll save you the seeks in the  
index... of course you'll have problems with file permissions etc, not  
mentioning security, locking, etc, etc, etc, is that worth the trouble ?

On Wed, 3 Nov 2004 14:35:28 -0500, Andrew Sullivan <ajs@crankycanuck.ca>  
wrote:

> 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.
>





view thread (12+ messages)  latest in thread

Message-ID: <opsgwmpq0fcq72hf@musicbox>
Permalink:  ../opsgwmpq0fcq72hf@musicbox/
Also on:    postgresql.org/message-id/opsgwmpq0fcq72hf@musicbox

 · 

reply

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: lists@boutiquenumerique.com
  Subject: Re: preloading indexes
  In-Reply-To: <opsgwmpq0fcq72hf@musicbox>

* 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