May 24, 2012

Post: Avoiding auto-increment holes on InnoDB with INSERT IGNORE

lock algorithm for the auto_increment value is configurable and you can select from different algorithms using the innodb_autoinc_lockAUTO_INCREMENT, `name` int(11) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `uniqname` (`name`) ) ENGINE=InnoDB AUTO_INCREMENT

Post: InnoDB auto-inc scalability fixed

… with InnoDB auto-increment field. For details check Bug 16979. In short words the problem is in case of insert into table with auto-increment column the special AUTO_INC table level lock is obtained, instead of usual row-level locks. With many concurrent…

Post: Improved InnoDB fast index creation

… | 0.000008 | | Opening tables | 0.000118 | | System lock | 0.000007 | | setup | 0.000027 | | creating table… slower; mysqldump –innodb-optimize-keys ignores indexes on AUTO_INCREMENT columns, because…InnoDB picks such an index as the clustered one. References: Peter’s post MySQL bug #57583 MySQL bug

Post: MyISAM Scalability and Innodb, Falcon Benchmarks

… PRIMARY KEY (`id`), KEY `val` (`val`) ) ENGINE=MyISAM AUTO_INCREMENT=4097 Table t1 contains about 260,000 records,…key cache locking was done so disk IO is not done while lock is held, while lock is … comparison of MyISAM Innodb and Falcon results in the graphical form: I’ve created bug, for MyISAM …

Post: Heikki Tuuri answers to Innodb questions, Part II

… of micro optimizations in Innodb in 5.0 series. Also note the “Auto Increment Issue” is finally … recently found and fixed: http://bugs.mysql.com/bug.php?id=29560 Concerning a switch to … should be possible to implement online reorganize which locks and reorganizes small portions of table online. Q38…

Post: Instrumentation and the cost of Foreign Keys

AUTO_INCREMENT, bogus_column char(32), PRIMARY KEY (id) ) ENGINE=InnoDB; CREATE TABLE child ( id INT NOT NULL AUTO_INCREMENTlock_trx_id: 87035 lock_mode: X lock_type: RECORD lock_table: `test`.`parent` lock_index: `PRIMARY` lock_space: 1300 lock_page: 3 lock_rec: 6 lock… Server.  See BUG #53336 …

Post: Percona Server 5.1.59-13.0

…on MySQL 5.1.59, including all the bug fixes in it, Percona Server 5.1….makes prefetch simple but has high overhead from locking rows only to undo changes at rollback. … Kopytov). Fixed assertion failure in InnoDB. #814404 (Yasufumi Kinoshita). Since AUTO_INCREMENT columns must be defined as keys…

Post: Percona Server 5.5.16-22.0

… on MySQL 5.5.16, including all the bug fixes in it, Percona Server 5.5…. makes prefetch simple but has high overhead from locking rows only to undo changes at rollback. …Oleg Tsarev). Fixed assertion failure in InnoDB. #814404 (Yasufumi Kinoshita). Since AUTO_INCREMENT columns must be defined as keys…

Comment: InnoDB auto-inc scalability fixed

[...] MySQL InnoDB 的 auto-increment 會造成 INSERT 時使用 table-level lock 的 bug 終於修正 (從 2006 年一月就進 MySQL 回報系統的 bug),下個 5.1 的版本 (預定是 5.1.22) 就會包括在裡面:InnoDB auto-inc scalability fixed。 [...]