| From: | Harald Fuchs <hf0722x(at)protecting(dot)net> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Caching of Queries |
| Date: | 2004-09-27 16:15:35 |
| Message-ID: | puzn3bg02g.fsf@srv.protecting.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
In article <1096261381(dot)25688(dot)741(dot)camel(at)localhost(dot)localdomain>,
Neil Conway <neilc(at)samurai(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Werman | 2004-09-27 16:43:38 | Re: Caching of Queries |
| Previous Message | Bruce Momjian | 2004-09-27 14:17:56 | Re: Caching of Queries |