Bug #70775 | Docs advice on query cache might be misleading | ||
---|---|---|---|
Submitted: | 30 Oct 2013 19:11 | Modified: | 29 Sep 2017 23:00 |
Reporter: | Morgan Tocker | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[30 Oct 2013 19:11]
Morgan Tocker
[31 Oct 2013 4:45]
MySQL Verification Team
Hello Morgan, Thank you for the valuable feedback. Thanks, Umesh
[24 Jun 2014 14:58]
Morgan Tocker
A few other pages that could potentially be updated: * http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html -> Some users with unoptimized queries may be caught with suddenly slower queries. Here is an example: http://dba.stackexchange.com/questions/66774/why-query-cache-type-is-disabled-by-default-s... * http://dev.mysql.com/doc/refman/5.6/en/query-cache.html -> Needs a warning.
[29 Sep 2017 23:00]
Paul DuBois
Posted by developer: Removed the text in question. Seems the best course of action, particularly since the query cache is now deprecated in MySQL 5.7 and removed in 8.0.