Re: preloading indexes
От
Andrew Sullivan
Тема
Re: preloading indexes
Дата
Msg-id
20041103193528.GB16528@phlogiston.dyndns.org
Ответ на
Список
Дерево обсуждения
preloading indexes <stuff@opensourceonline.com>
Re: preloading indexes "Matt Clark" <matt@ymogen.net>
Re: preloading indexes <stuff@opensourceonline.com>
Re: preloading indexes Andrew Sullivan <ajs@crankycanuck.ca>
Re: preloading indexes <stuff@opensourceonline.com>
Re: preloading indexes Tom Lane <tgl@sss.pgh.pa.us>
Re: preloading indexes Mike Benoit <ipso@snappymail.ca>
Re: preloading indexes <stuff@opensourceonline.com>
Re: preloading indexes Andrew Sullivan <ajs@crankycanuck.ca>
Re: preloading indexes Andrew Sullivan <ajs@crankycanuck.ca>
Re: preloading indexes Pierre-Frédéric Caillaud<lists@boutiquenumerique.com>
Re: preloading indexes Tom Lane <tgl@sss.pgh.pa.us>
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 по дате отправления