From: Josh Berkus <josh@agliodbs.com>
To: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Sat, 2 Oct 2004 15:50:58 -0700
Message-ID: <200410021550.58484.josh@agliodbs.com> (raw)
In-Reply-To: <cjn41a$274m$1@news.hub.org>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<200410021304.21281.josh@agliodbs.com>
<cjn41a$274m$1@news.hub.org>
William,
> 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.
Oddly, Joe Conway just mentioned the same idea to me.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, wyu@talisys.com
Subject: Re: Caching of Queries
In-Reply-To: <200410021550.58484.josh@agliodbs.com>
* 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