From: Jim C. Nasby <decibel@decibel.org>
To: Josh Berkus <josh@agliodbs.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Caching of Queries
Date: Mon, 4 Oct 2004 14:18:50 -0500
Message-ID: <20041004191850.GS1297@decibel.org> (raw)
In-Reply-To: <200410011010.40705.josh@agliodbs.com>
References: <00e801c4a4b6$5526dd30$8300a8c0@solent>
<20040930221107.GP1297@decibel.org>
<415CEE8E.8060805@ymogen.net>
<200410011010.40705.josh@agliodbs.com>
On Fri, Oct 01, 2004 at 10:10:40AM -0700, Josh Berkus wrote:
> Transparent "query caching" is the "industry standard" for how these things
> are handled. However, Postgres' lack of this feature has made me consider
> other approaches, and I'm starting to wonder if the "standard" query caching
> -- where a materialized query result, or some reduction thereof, is cached in
> database memory -- isn't the best way to cache things. I'm going to
> abbreviate it "SQC" for the rest of this e-mail.
Not to quibble, but are you sure that's the standard? Oracle and DB2
don't do this, and I didn't think MSSQL did either. What they do do is
cache query *plans*. This is a *huge* deal in Oracle; search
http://asktom.oracle.com for 'soft parse'.
In any case, I think a means of marking some specific queries as being
cachable is an excellent idea; perfect for 'static data' scenarios. What
I don't know is how much will be saved.
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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: decibel@decibel.org, josh@agliodbs.com
Subject: Re: Caching of Queries
In-Reply-To: <20041004191850.GS1297@decibel.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