| From: | Hartmut Holzgraefe <hartmut(dot)holzgraefe(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-07 08:41:11 |
| Message-ID: | efadf884-a7ab-dcf9-28df-bbb3e91b4355@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07.05.2018 10:12, Konstantin Knizhnik wrote:
> Concerning result cache, I think it will be better to ask opinion of
> mysql users: how useful it is.
It isn't useful. I haven't seen a customer case in years where the query
cache would have done any good.
It is off by default ever since MySQL 5.5 (became "GA" in 2010), and
has now finally been removed from MySQL 8.0. It is still there in
MariaDB, and as far as I can tell there are no plans to remove it
yet, at least not in the next two major releases 10.3 and 10.4.
At the same time we (wearing my MariaDB Corp. hat right now) have
added a "time-to-live" cache module to our MaxScale proxy solution,
so moving caching out of the server for use cases where a time-to-live
cache is "good enough" and immediate cache entry invalidation on
changes of underlying data is not a requirement, so that getting
outdated results back if they are not too old is OK.
--
Hartmut Holzgraefe, Principal Support Engineer (EMEA)
MariaDB Corporation | http://www.mariadb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2018-05-07 08:41:59 | Re: Having query cache in core |
| Previous Message | Tsunakawa, Takayuki | 2018-05-07 08:24:27 | RE: Having query cache in core |