X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 06C2E3A2B1B for ; Wed, 3 Nov 2004 19:35:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 65316-02 for ; Wed, 3 Nov 2004 19:35:36 +0000 (GMT) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by svr1.postgresql.org (Postfix) with SMTP id 99BEA3A45F0 for ; Wed, 3 Nov 2004 19:35:34 +0000 (GMT) Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@65.49.125.184 with login) by smtp102.rog.mail.re2.yahoo.com with SMTP; 3 Nov 2004 19:35:30 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id E8D24404B; Wed, 3 Nov 2004 14:35:28 -0500 (EST) Date: Wed, 3 Nov 2004 14:35:28 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: preloading indexes Message-ID: <20041103193528.GB16528@phlogiston.dyndns.org> Mail-Followup-To: pgsql-performance@postgresql.org References: <004b01c4c1ce$cd969c80$8300a8c0@solent> <20041103191247.GFZT27576.fed1rmmtao07.cox.net@CYGNUS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041103191247.GFZT27576.fed1rmmtao07.cox.net@CYGNUS> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/22 X-Sequence-Number: 8976 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