From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Sat, 02 Oct 2004 13:47:26 -0700
Message-ID: <cjn41a$274m$1@news.hub.org> (raw)
In-Reply-To: <200410021304.21281.josh@agliodbs.com>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<200410011010.40705.josh@agliodbs.com>
<BAY18-DAV14hd2stb2e0004dade@hotmail.com>
<200410021304.21281.josh@agliodbs.com>
Josh Berkus wrote:
> 1) Query caching is not a single problem, but rather several different
> problems requiring several different solutions.
>
> 2) Of these several different solutions, any particular query result caching
> implementation (but particularly MySQL's) is rather limited in its
> applicability, partly due to the tradeoffs required. Per your explanation,
> Oracle has improved this by offering a number of configurable options.
>
> 3) Certain other caching problems would be solved in part by the ability to
> construct "in-memory" tables which would be non-durable and protected from
> cache-flushing. This is what I'm interested in chatting about.
Just my 2 cents on this whole issue. I would lean towards having result
caching in pgpool versus the main backend. I want every ounce of memory
on a database server devoted to the database. Caching results would
double the effect of cache flushing ... ie, now both the results and the
pages used to build the results are in memory pushing out other stuff to
disk that may be just as important.
If it was in pgpool or something similar, I could devote a separate
machine just for caching results leaving the db server untouched.
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: wyu@talisys.com
Subject: Re: Caching of Queries
In-Reply-To: <cjn41a$274m$1@news.hub.org>
* 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