Bug #80312 maximum_query_cache_size cannot be set

Submitted: 9 Feb 2016 8:14 Modified: 23 Sep 2025 14:05
Reporter: Tsubasa Tanaka (OCA) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version:5.7.11 OS:CentOS (6.6)
Assigned to: CPU Architecture:Any

[9 Feb 2016 8:14] Tsubasa Tanaka
Description:
Doc says "You can set the maximum size that can be specified for the query cache at runtime with the SET statement by using the --maximum-query_cache_size=32M option on the command line or in the configuration file.", but that option cannot be set.

http://dev.mysql.com/doc/refman/5.7/en/query-cache-configuration.html

How to repeat:
# yum install -y http://dev.mysql.com/get/mysql57-community-release-el6-7.noarch.rpm
# yum install -y mysql-community-server
# echo "maximum_query_cache_size= 128M" >> /etc/my.cnf
# service mysqld start
Initializing MySQL database:  2016-02-09T08:08:53.675028Z 0 [ERROR] /usr/sbin/mysqld: Maximum value of 'query_cache_size' cannot be set
2016-02-09T08:08:53.675139Z 0 [ERROR] Aborting

                                                           [FAILED]
[9 Feb 2016 8:21] MySQL Verification Team
Hello Tanaka-San,

Thank you for the report.

Thanks,
Umesh
[23 Sep 2025 14:05] Marc ALFF
The query cache is deprecated as of MySQL 5.7.20, and is removed in MySQL 8.0.

Closing this bug, no longer relevant.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.