| From: | "Matt Clark" <matt(at)ymogen(dot)net> |
|---|---|
| To: | <stuff(at)opensourceonline(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: preloading indexes |
| Date: | 2004-11-03 17:59:02 |
| Message-ID: | 004b01c4c1ce$cd969c80$8300a8c0@solent |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)postgresql(dot)org
[mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
stuff(at)opensourceonline(dot)com
Sent: 03 November 2004 17:31
To: pgsql-performance(at)postgresql(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | patrick ~ | 2004-11-03 18:56:47 | vacuum analyze slows sql query |
| Previous Message | stuff | 2004-11-03 17:30:47 | preloading indexes |