From: Rod Taylor <rbt@rbt.ca>
To: Wei Weng <wweng@kencast.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Chris Faulkner <chrisf@oramap.com>
Cc: Pgsql-Performance <pgsql-performance@postgresql.org>
Cc: Pgsql-Sql <pgsql-sql@postgresql.org>
Subject: Re: sql performance and cache
Date: Tue, 14 Oct 2003 14:15:39 -0400
Message-ID: <1066155338.63280.7.camel@jester> (raw)
In-Reply-To: <Pine.LNX.4.56.0310141247370.7836@localhost.localdomain>
References: <DGENKIKMJILAAKJGFHKFEEKECIAA.chrisf@oramap.com>
<3F87D764.8030306@familyhealth.com.au>
<Pine.LNX.4.56.0310141247370.7836@localhost.localdomain>
> > Perhaps you are confusing it with the MySQL query cache?
> Is there plan on developing one (query cache)?
For the most part, prepared queries and cursors give you a greater
advantage due to their versatility -- both of which we do have.
In the cases where an actual cache is useful, the client application
could do it just as easily or temp tables can be used.
I suspect it would be implemented more as a caching proxy than as an
actual part of PostgreSQL, should someone really want this feature.
Attachments:
signature.asc (application/pgp-signature, 186B) download
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-sql@postgresql.org
Cc: rbt@rbt.ca, wweng@kencast.com, chriskl@familyhealth.com.au, chrisf@oramap.com, pgsql-performance@postgresql.org
Subject: Re: sql performance and cache
In-Reply-To: <1066155338.63280.7.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