The branch, master has been updated via 7ea269797d9bcc1c062bd46f2986b78501bdac3f (commit) from a466c8fa50325a2aae0212ee958233e8bb9fc8d5 (commit)

- Log ----------------------------------------------------------------- commit 7ea269797d9bcc1c062bd46f2986b78501bdac3f Author: Marc Delisle marc@infomarc.info Date: Wed Nov 2 15:29:12 2011 -0400

Typo

-----------------------------------------------------------------------

Summary of changes: libraries/advisory_rules.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/libraries/advisory_rules.txt b/libraries/advisory_rules.txt index 9ab0043..f724ddf 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -422,7 +422,7 @@ rule 'Max InnoDB log size' [innodb_buffer_pool_size > 0 && innodb_log_file_size 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> - Your absolute InnoD log size is %s MiB | round(value,1) + Your absolute InnoDB log size is %s MiB | round(value,1)

rule 'InnoDB buffer pool size' [system_memory > 0] innodb_buffer_pool_size / system_memory * 100

hooks/post-receive