|
Thanks, I am already have started doing that. i.e. running the dummy task to get the tables loaded again and it worked fine today. regards Alex > To: aintokyo@xxxxxxxxxxx > CC: scott.marlowe@xxxxxxxxx; pgsql-general@xxxxxxxxxxxxxx > Subject: Re: PL/Perl Performance Problems > Date: Sun, 20 Dec 2009 22:39:00 -0500 > From: tgl@xxxxxxxxxxxxx > > Alex - <aintokyo@xxxxxxxxxxx> writes: > > Tom, Scott, Alvaro,thanks for the hints on this issue. It looks as if one of the EOD maintenance jobs which does a few extensive 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 > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general Check out the latest features today Get more out of Hotmail |
