Comments on: Concurrent inserts on MyISAM and the binary log http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/ Everything about MySQL Performance Sat, 21 Nov 2009 05:23:57 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: WB http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-372406 WB Tue, 04 Nov 2008 11:56:54 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-372406 Maybe, using SET SQL_LOG_BIN=0, this problem con't be solved? Maybe, using SET SQL_LOG_BIN=0, this problem con’t be solved?

]]> By: esudnik http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-315114 esudnik Thu, 19 Jun 2008 12:25:20 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-315114 ...of course it is not a solution for all cases ;-) …of course it is not a solution for all cases ;-)

]]> By: esudnik http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-315113 esudnik Thu, 19 Jun 2008 12:24:33 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-315113 To avoid table locks with MyISAM I use INSERT DELAYED (http://dev.mysql.com/doc/refman/5.0/en/insert-delayed.html) statements. To avoid table locks with MyISAM I use INSERT DELAYED (http://dev.mysql.com/doc/refman/5.0/en/insert-delayed.html) statements.

]]> By: Rob http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-302133 Rob Tue, 20 May 2008 19:36:00 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-302133 Do you mean use innodb with 5.1? On 5.0 the behaviour is the same for innodb. I don't think you can get around the issue without running with "innodb_locks_unsafe_for_binlog=1" which was mentioned here: http://www.mysqlperformanceblog.com/2006/07/12/insert-into-select-performance-with-innodb-tables/ Do you mean use innodb with 5.1? On 5.0 the behaviour is the same for innodb. I don’t think you can get around the issue without running with “innodb_locks_unsafe_for_binlog=1″ which was mentioned here:

http://www.mysqlperformanceblog.com/2006/07/12/insert-into-select-performance-with-innodb-tables/

]]> By: peter http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-299363 peter Thu, 15 May 2008 21:18:05 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-299363 Right. Looks like potential future improvement :) Right. Looks like potential future improvement :)

]]> By: Baron Schwartz http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-299181 Baron Schwartz Thu, 15 May 2008 01:44:08 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-299181 I tried setting binlog_format=row in my.cnf, verified that it worked, and then ran an INSERT and an INSERT..SELECT. The results were the same: this code does not seem to be affected by the binary logging format at all. I tried setting binlog_format=row in my.cnf, verified that it worked, and then ran an INSERT and an INSERT..SELECT. The results were the same: this code does not seem to be affected by the binary logging format at all.

]]> By: peter http://www.mysqlperformanceblog.com/2008/05/14/concurrent-insert-select-myisam/comment-page-1/#comment-299111 peter Thu, 15 May 2008 00:27:36 +0000 http://www.mysqlperformanceblog.com/?p=397#comment-299111 Baron, What if you would use Row Level Replication in MySQL 5.1 - will this lock go away then ? Baron,

What if you would use Row Level Replication in MySQL 5.1 – will this lock go away then ?

]]>