From: Tom Lane <tgl@sss.pgh.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Aaron Werman <awerman@hotmail.com>
Cc: Scott Kirkwood <scottakirkwood@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Mon, 27 Sep 2004 01:18:56 -0400
Message-ID: <18766.1096262336@sss.pgh.pa.us> (raw)
In-Reply-To: <1096261381.25688.741.camel@localhost.localdomain>
References: <b3dc511704092212502a2ddb09@mail.gmail.com>
<BAY9-DAV21Y1SWoBDys0000cef5@hotmail.com>
<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.
Do they actually make a rigorous guarantee that the cached result is
still accurate when/if it is returned to the client? (That's an honest
question --- I don't know how MySQL implements this.)
IIRC, in our past threads on this topic, it was suggested that if you
can tolerate not-necessarily-up-to-date results, you should be doing
this sort of caching on the client side and not in the DB server at all.
I wouldn't try that in a true "client" scenario, but when the DB client
is application-server middleware, it would make some sense to cache in
the application server.
regards, tom lane
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: tgl@sss.pgh.pa.us, neilc@samurai.com, awerman@hotmail.com, scottakirkwood@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <18766.1096262336@sss.pgh.pa.us>
* 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