diff options
| author | Herman van Rink <rink@initfour.nl> | 2013-02-12 18:00:02 +0400 |
|---|---|---|
| committer | Herman van Rink <rink@initfour.nl> | 2013-02-12 18:00:02 +0400 |
| commit | 5b295a8916822fde812577291dc2aabc7cf4394c (patch) | |
| tree | 6c3d17b49095ef6219c77aeef8048f6c6f40f422 /libraries/advisory_rules.txt | |
| parent | 5e7e416dab2029c26535b80880b9879b2c2e375a (diff) | |
Place some more variable names between curly braces
Diffstat (limited to 'libraries/advisory_rules.txt')
| -rw-r--r-- | libraries/advisory_rules.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libraries/advisory_rules.txt b/libraries/advisory_rules.txt index 06a53403fc..043aa97c87 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -437,14 +437,14 @@ rule 'InnoDB log size' [innodb_buffer_pool_size > 0] innodb_log_file_size / innodb_buffer_pool_size * 100 value < 20 The InnoDB log file size is not an appropriate size, in relation to the InnoDB buffer pool. - Especially on a system with a lot of writes to InnoDB tables you should set innodb_log_file_size to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a> + Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a> Your InnoDB log size is at %s% in relation to the InnoDB buffer pool size, it should not be below 20% | round(value,1) rule 'Max InnoDB log size' [innodb_buffer_pool_size > 0 && innodb_log_file_size / innodb_buffer_pool_size * 100 < 30] innodb_log_file_size / (1024 * 1024) value >= 128 The InnoDB log file size is inadequately large. - It is usually sufficient to set innodb_log_file_size to 25% of the size of {innodb_buffer_pool_size}. A very big innodb_log_file_size slows down the recovery time after a database crash considerably. See also <a href="http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a> + It is usually sufficient to set {innodb_log_file_size} to 25% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows down the recovery time after a database crash considerably. See also <a href="http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a> Your absolute InnoDB log size is %s MiB | round(value,1) rule 'InnoDB buffer pool size' [system_memory > 0] |