From: Rod Taylor <pg@rbt.ca>
To: Chris Browne <cbbrowne@acm.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL caching
Date: Fri, 21 May 2004 14:33:54 -0400
Message-ID: <1085164433.20081.265.camel@jester> (raw)
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>
> 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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pg@rbt.ca, cbbrowne@acm.org
Subject: Re: PostgreSQL caching
In-Reply-To: <1085164433.20081.265.camel@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox