Re: PL/Perl Performance Problems - Mailing list pgsql-general

From Tom Lane
Subject Re: PL/Perl Performance Problems
Date
Msg-id 25812.1261366740@sss.pgh.pa.us
Whole thread Raw
In response to Re: PL/Perl Performance Problems  (Alex - <aintokyo@hotmail.com>)
Responses Re: PL/Perl Performance Problems  (Alex - <aintokyo@hotmail.com>)
List pgsql-general
Alex - <aintokyo@hotmail.com> writes:
> Tom, Scott, Alvaro,thanks for the hints on this issue. It looks as if one of the EOD maintenance jobs which does a
fewextensive queries does push data out of memory leading to this behavior.  
> Is there a way to permanently cash some tables into memory?

Not as such, and if there were it probably wouldn't be an overall
performance win anyway, because you'd hurt your maintenance tasks.
What you might consider doing is, at the end of the EOD sequence,
run some dummy queries that scan the tables you use normally, causing
them to get swapped back in so the cache is already primed when people
come to work in the morning.

            regards, tom lane

pgsql-general by date:

Previous
From: Alex -
Date:
Subject: Re: PL/Perl Performance Problems
Next
From: John DeSoi
Date:
Subject: Re: Extended Query, flush or sync ?