From: Matt Clark <matt@ymogen.net>
To: stuff@opensourceonline.com
To: pgsql-performance@postgresql.org
Subject: Re: preloading indexes
Date: Wed, 3 Nov 2004 17:59:02 -0000
Message-ID: <004b01c4c1ce$cd969c80$8300a8c0@solent> (raw)
In-Reply-To: <20041103173054.EJWF21506.fed1rmmtao05.cox.net@CYGNUS>
The best way to get all the stuff needed by a query into RAM is to run the
query. Is it more that you want to 'pin' the data in RAM so it doesn't get
overwritten by other queries?
-----Original Message-----
From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of
stuff@opensourceonline.com
Sent: 03 November 2004 17:31
To: pgsql-performance@postgresql.org
Subject: [PERFORM] preloading indexes
I am working with some pretty convoluted queries that work very slowly the
first time they're called but perform fine on the second call. I am fairly
certain that these differences are due to the caching. Can someone point me
in a direction that would allow me to pre-cache the critical indexes?
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: matt@ymogen.net, stuff@opensourceonline.com
Subject: Re: preloading indexes
In-Reply-To: <004b01c4c1ce$cd969c80$8300a8c0@solent>
* 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