Mysql 5.5 concurrent_insert different values than previous versions

Bug #803472 reported by CyberCr33p
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL Tuning Primer Script
Fix Released
Medium
TodoInTX

Bug Description

concurrent_insert on mysql 5.5 uses values AUTO, NEVER and ALWAYS, instead of 1, 0 and 2.

TodoInTX (matt-day32)
Changed in mysql-tuning-primer:
importance: Undecided → Medium
assignee: nobody → TodoInTX (matt-day32)
status: New → Confirmed
Revision history for this message
Markus M. (markus-mi) wrote :

At line 1181 replace:

if [ $concurrent_insert -le 1 ] && [ "$mysql_version_num" -gt 050000 ] ; then
cecho "If you have a high concurrency of inserts on Dynamic row-length tables"
cecho "consider setting 'concurrent_insert=2'."
fi

with:

if [ "$mysql_version_num" -gt 050000 ] && [ "$mysql_version_num" -lt 050500 ]; then
 if [ $concurrent_insert -le 1 ] ; then
  cecho "If you have a high concurrency of inserts on Dynamic row-length tables"
  cecho "consider setting 'concurrent_insert=2'."
 fi
elif [ "$mysql_version_num" -gt 050500 ] ; then
 if [ "$concurrent_insert" = 'AUTO' ] || [ "$concurrent_insert" = 'NEVER' ] ; then
  cecho "If you have a high concurrency of inserts on Dynamic row-length tables"
  cecho "consider setting 'concurrent_insert=2'."
 fi
fi

Thank it should work for MySQL 5.5, too.

Revision history for this message
TodoInTX (matt-day32) wrote :

Markus M.

Thank you for the very nice patch. I have merged and committed the fix at revision 23

Changed in mysql-tuning-primer:
status: Confirmed → Fix Committed
TodoInTX (matt-day32)
Changed in mysql-tuning-primer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.