From: Harald Fuchs <hf0722x@protecting.net>
To: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: 23 Sep 2004 16:24:46 +0200
Message-ID: <pud60dgj0x.fsf@srv.protecting.net> (raw)
References: <b3dc511704092212502a2ddb09@mail.gmail.com>
In article <b3dc511704092212502a2ddb09@mail.gmail.com>,
Scott Kirkwood <scottakirkwood@gmail.com> writes:
> I couldn't find anything in the docs or in the mailing list on this,
> but it is something that Oracle appears to do as does MySQL.
> The idea, I believe, is to do a quick (hash) string lookup of the
> query and if it's exactly the same as another query that has been done
> recently to re-use the old parse tree.
That's not was MySQL is doing. MySQL caches not the query plan, but
the result set for the (hashed) query string. If the same query comes
again, it is not executed at all (unless one of the tables involved
have been changed meanwhile).
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: hf0722x@protecting.net
Subject: Re: Caching of Queries
In-Reply-To: <pud60dgj0x.fsf@srv.protecting.net>
* 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