[Phpmyadmin-git] [SCM] phpMyAdmin branch, master, updated. RELEASE_3_4_7-22133-g4e2533f

Marc Delisle lem9 at users.sourceforge.net
Wed Nov 2 20:18:09 CET 2011


The branch, master has been updated
       via  4e2533f506fff9dfd894de9cbfda7e280892c614 (commit)
      from  362f7ab3033caa7217ba5d67662dd1a41d16b120 (commit)


- Log -----------------------------------------------------------------
commit 4e2533f506fff9dfd894de9cbfda7e280892c614
Author: Marc Delisle <marc at infomarc.info>
Date:   Wed Nov 2 15:17:48 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 f2db089..a94f756 100644
--- a/libraries/advisory_rules.txt
+++ b/libraries/advisory_rules.txt
@@ -414,7 +414,7 @@ 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 one 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]


hooks/post-receive
-- 
phpMyAdmin




More information about the Git mailing list