From: Harald Fuchs <hf0722x@protecting.net>
To: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: 27 Sep 2004 18:15:35 +0200
Message-ID: <puzn3bg02g.fsf@srv.protecting.net> (raw)
References: <b3dc511704092212502a2ddb09@mail.gmail.com>
<BAY9-DAV21Y1SWoBDys0000cef5@hotmail.com>
<1096261381.25688.741.camel@localhost.localdomain>
In article <camel@localhost.localdomain/">1096261381.25688.741.camel@localhost.localdomain>,
Neil Conway <neilc@samurai.com> writes:
> I think the conclusion of past discussions about this feature is that
> it's a bad idea. Last I checked, MySQL has to clear the *entire* query
> cache when a single DML statement modifying the table in question is
> issued.
Nope, it deletes only queries using that table.
> Not to mention that the feature is broken for non-deterministic
> queries (like now(), ORDER BY random(), or nextval('some_seq'), and so
> on).
Queries containing now(), rand(), or similar functions aren't cached by MySQL.
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: <puzn3bg02g.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