From: Martin Nickel <martin@portant.com>
Subject: What gets cached?
Date: Fri, 21 Oct 2005 07:34:30 -0500
Organization: Hub.Org Networking Services
Lines: 15
Message-ID: <pan.2005.10.21.12.34.29.712700@portant.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing
	moment of clarity.)
To: pgsql-performance@postgresql.org

I was reading a comment in another posting and it started me thinking
about this.  Let's say I startup an Oracle server.  All my queries are a
little bit (sometimes a lot bit) slow until it gets its "normal" things in
memory, then it's up to speed.  The "normal" things would include some
small lookup tables and the indexes for the most frequently used tables.

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".  

Does this seem true?
 s