Bug #30087 Set query_cache_size, if the value is too small, get a unclear warning
Submitted: 27 Jul 2007 1:08 Modified: 25 Nov 2008 14:40
Reporter: q a Email Updates:
Status: Patch approved
Category:Server Severity:S3 (Non-critical)
Version:5.0.45 OS:Any
Assigned to: Kristofer Pettersson Target Version:
Triage: Triaged: D3 (Medium)

[27 Jul 2007 1:08] q a 
Description:
When set query_cache_size less than 41893, I got a warning:
Warning 1282  Query cache failed to set size 40960; new query cache size is 0 

How to repeat:
set global query_cache_size=8000;
The warning will come out.

Suggested fix:
Would you make the warning more clear? I mean, from current warning, we can not know it's
because the value is too small that we can not set it. 
And you'd better indicate what is the acceptable minimal value.
[27 Jul 2007 1:20] Miguel Solorzano 
Thank you for the bug report.
[11 Mar 2008 23:31] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/43746

ChangeSet@1.2594, 2008-03-11 11:13:51+01:00, thek@adventure.(none) +5 -0
  Bug#30087 Set query_cache_size, if the value is too small, get a unclear warning
  
  This bugs clarifies a warning message issued when the query cache data
  size becomes smaller than the minium allowed size.
[11 Mar 2008 23:57] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/43767

ChangeSet@1.2594, 2008-03-11 14:50:41+01:00, thek@adventure.(none) +5 -0
  Bug#30087 Set query_cache_size, if the value is too small, get a unclear warning
  
  This bugs clarifies a warning message issued when the query cache data
  size becomes smaller than the minium allowed size.
[17 Mar 2008 14:25] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/44110

ChangeSet@1.2594, 2008-03-17 15:32:18+01:00, thek@adventure.(none) +5 -0
  Bug#30087 Set query_cache_size, if the value is too small, get a unclear warning
  
  This bugs clarifies a warning message issued when the query cache data
  size becomes smaller than the minium allowed size.
[18 Mar 2008 11:46] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/44169

ChangeSet@1.2594, 2008-03-18 12:54:46+01:00, thek@adventure.(none) +5 -0
  Bug#30087 Set query_cache_size, if the value is too small, get a unclear warning
  
  This bugs clarifies a warning message issued when the query cache data
  size becomes smaller than the minium allowed size.
[16 Jul 2008 22:29] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/49894
[16 Jul 2008 22:38] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/49896
[17 Jul 2008 14:36] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/49934

2644 Georgi Kodinov	2008-07-17
      Folow-up on Bug#37069: fix a valgrind warning
      Don't initalize federated if it's disabled by a command line option.
[18 Jul 2008 13:56] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/50038

2644 Kristofer Pettersson	2008-07-24
      Bug#37027 expire_logs_days and missing binlogs cause a crash !
      
      If the server failed to expired log files during start up it could crash.
[22 Jul 2008 18:35] Bugs System 
Pushed into 5.0.68
[22 Jul 2008 18:38] Bugs System 
Pushed into 5.0.66
[28 Jul 2008 13:46] Bugs System 
Pushed into 5.0.68  (revid:marc.alff@sun.com-20080716222922-hlmk0lyj2seeb1ag) (pib:2)
(Retry automatic marking, to ensure nothing is missed. cm01)
[28 Jul 2008 14:44] Bugs System 
Pushed into 6.0.7-alpha  (revid:alik@mysql.com-20080725172155-fnc73o50e4tgl23k) (version
source revid:alik@mysql.com-20080725172155-fnc73o50e4tgl23k) (pib:3)
[28 Jul 2008 16:44] Bugs System 
Pushed into 5.1.28  (revid:davi.arnaut@sun.com-20080722182431-0i2f1yc4uocime9q) (version
source revid:davi.arnaut@sun.com-20080722182431-0i2f1yc4uocime9q) (pib:3)
[14 Sep 2008 0:59] Bugs System 
Pushed into 6.0.7-alpha  (revid:kpettersson@mysql.com-20080619004035-kyyos3dh9lwbn3vv)
(version source revid:vvaintroub@mysql.com-20080804094710-jb2qpqxpf2ir2gf3) (pib:3)