ernel disk cache by accessing a whole lot of non-Postgres stuff.
(A nightly disk backup is one obvious candidate.) The most likely
solution is to run some cron job a little later to exercise your
database and thereby repopulate the cache with Postgres files before
you get to work ;-)
The caching appears to disappear overnight. The environment is not in
production yet so I'm the only one on it.
Is there a time limit on the length of time in cache? I believe there is
sufficient RAM, but maybe I need to look again.
s
-Original Message-
From: [EMAIL PROTECTED]
[mailto:
Title: Message
That’s correct – I’d
like to be able to keep particular indexes in RAM available all the time
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 overw
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
inde