The branch, master has been updated via 2074bd87b1ddfab89fe5c522825e1f5a338598a2 (commit) via 7ead858d587c2e62b3015b965acda2c4d9378280 (commit) from d1803b5aee4b35e5166329daa3790de5aea6df20 (commit)
- Log ----------------------------------------------------------------- commit 2074bd87b1ddfab89fe5c522825e1f5a338598a2 Merge: 7ead858 d1803b5 Author: Marc Delisle marc@infomarc.info Date: Thu Aug 11 09:14:25 2011 -0400
Merge branch 'master' of ssh://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin
commit 7ead858d587c2e62b3015b965acda2c4d9378280 Author: Marc Delisle marc@infomarc.info Date: Thu Aug 11 09:14:01 2011 -0400
More typos
-----------------------------------------------------------------------
Summary of changes: 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 8941148..edbdb7b 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -240,14 +240,14 @@ rule '% temp disk tables' [Created_tmp_tables + Created_tmp_disk_tables > 0] Created_tmp_disk_tables / (Created_tmp_tables + Created_tmp_disk_tables) * 100 value > 25 Many temporary tables are being written to disk instead of being kept in memory. - Increasing {max_heap_table_size} and {tmp_table_size} might help. However some temporary tables are always being written to disk, independent of the value of these variables. To elminiate these you will have to rewrite your queries to avoid those conditions (Within a temporary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in the beginning of an <a href="http://www.facebook.com/note.php?note_id=10150111255065841&comments">Article by the Pythian Group</a> + Increasing {max_heap_table_size} and {tmp_table_size} might help. However some temporary tables are always being written to disk, independent of the value of these variables. To eliminate these you will have to rewrite your queries to avoid those conditions (Within a temporary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in the beginning of an <a href="http://www.facebook.com/note.php?note_id=10150111255065841&comments">Article by the Pythian Group</a> %s% of all temporary tables are being written to disk, this value should be below 25% | round(value,1)
rule 'temp disk rate' Created_tmp_disk_tables / Uptime value * 60 * 60 > 1 Many temporary tables are being written to disk instead of being kept in memory. - Increasing {max_heap_table_size} and {tmp_table_size} might help. However some temporary tables are always being written to disk, independent of the value of these variables. To elminiate these you will have to rewrite your queries to avoid those conditions (Within a temprorary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in in the <a href="http://dev.mysql.com/doc/refman/5.0/en/internal-temporary-tables.html">MySQL Documentation</a> + Increasing {max_heap_table_size} and {tmp_table_size} might help. However some temporary tables are always being written to disk, independent of the value of these variables. To eliminate these you will have to rewrite your queries to avoid those conditions (Within a temprorary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in in the <a href="http://dev.mysql.com/doc/refman/5.0/en/internal-temporary-tables.html">MySQL Documentation</a> Rate of temporay tables being written to disk: %s, this value should be less than 1 per hour | PMA_bytime(value,2)
# I couldn't find any source on the internet that suggests a direct relation between high counts of temporary tables and any of these variables.
hooks/post-receive