On Fri, Oct 21, 2005 at 07:34:30AM -0500, Martin Nickel wrote: > Let's say I do the same thing in Postgres. I'm likely to have my very > fastest performance for the first few queries until memory gets filled up. > The only time Postgres seems to take advantage of cached data is when I > repeat the same (or substantially the same) query. I don't know of any > way to view what is actually cached at any point in time, but it seems > like "most recently used" rather than "most frequently used".
What version are you using? There have been significant improvements to the buffer manager in the last few versions. Most of the caching is done by your OS, though, so that would probably influence the results quite a bit. /* Steinar */ -- Homepage: http://www.sesse.net/ ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
