Re: Per-table random_page_cost for tables that we know are always cached

From: Decibel! <decibel(at)decibel(dot)org>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: PFC <lists(at)peufeu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Per-table random_page_cost for tables that we know are always cached
Date: 2008-04-24 16:07:49
Message-ID: 3FA47641-ABEA-4C6E-87D4-8EF3CAFC114F@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-04-24 16:11:30 Re: Is this TODO item done?
Previous Message Tom Lane 2008-04-24 16:04:47 Re: Is this TODO item done?