The branch, master has been updated via 1c872ed13345460c43fd363ba50fc03bc0e7dbbc (commit) from 6b786f7c55dd6419533b2d3b82685a375f498195 (commit)

- Log ----------------------------------------------------------------- commit 1c872ed13345460c43fd363ba50fc03bc0e7dbbc Author: Marc Delisle marc@infomarc.info Date: Wed Oct 5 12:56:33 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 1bc5023..8216a49 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -255,7 +255,7 @@ rule 'Temp disk rate' 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 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.5/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) + Rate of temporary 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. # Several independent Blog entries suggest (http://ronaldbradford.com/blog/more-on-understanding-sort_buffer_size-2010-0... and http://www.xaprb.com/blog/2010/05/09/how-to-tune-mysqls-sort_buffer_size/)

hooks/post-receive