Re: Per-table random_page_cost for tables that we know are always cached - Mailing list pgsql-hackers

From Decibel!
Subject Re: Per-table random_page_cost for tables that we know are always cached
Date
Msg-id 3FA47641-ABEA-4C6E-87D4-8EF3CAFC114F@decibel.org
Whole thread Raw
In response to Re: Per-table random_page_cost for tables that we know are always cached  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-hackers
On Apr 23, 2008, at 12:31 AM, Greg Smith wrote:
> Jim threw out that you can just look at the page hit percentages  
> instead. That's not completely true.  If you've had some nasty  
> query blow out your buffer cache, or if the server has been up a  
> looong time and the total stas don't really reflect recent reality,  
> what's in the buffer cache and what the stats say have been  
> historical cached can diverge.


Yeah, I kinda hand-waved over that. Obviously we'd want to look at  
recent stats, not beginning of time.
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is this TODO item done?
Next
From: Bruce Momjian
Date:
Subject: Re: Is this TODO item done?