X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 7FF35D1B896
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 21 May 2004 15:34:26 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 81395-03
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 21 May 2004 15:34:07 -0300 (ADT)
Received: from tht.net (vista.tht.net [216.126.88.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 09C34D1B196
	for <pgsql-performance@postgresql.org>;
	Fri, 21 May 2004 15:33:56 -0300 (ADT)
Received: from [134.22.68.4] (dyn-68-4.tor.dsl.tht.net [134.22.68.4])
	by tht.net (Postfix) with ESMTP
	id 3715676B0C; Fri, 21 May 2004 14:33:59 -0400 (EDT)
Subject: Re: PostgreSQL caching
From: Rod Taylor <pg@rbt.ca>
To: Chris Browne <cbbrowne@acm.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
In-Reply-To: <604qq9hez9.fsf@dev6.int.libertyrms.info>
References: <40782517171.20040521174209@012.net.il>
	<40AE2174.7060107@archonet.com>
	<604qq9hez9.fsf@dev6.int.libertyrms.info>
Content-Type: text/plain
Message-Id: <1085164433.20081.265.camel@jester>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Fri, 21 May 2004 14:33:54 -0400
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200405/184
X-Sequence-Number: 7015

> What is essentially required is the "prescient cacheing algorithm,"
> where the postmaster must consult /dev/esp in order to get a
> prediction of what blocks it may need to refer to in the next sixty
> seconds.

Easy enough. Television does it all the time with live shows. The guy
with the buzzer always seems to know what will be said before they say
it. All we need is a 5 to 10 second delay...