… the form of fixes for bug 51325 and bug 64284. So what is this blog…page): Release the shared lock on the latch protecting the AHI Lock the page in … t_x(i int(11) not null auto_increment primary key) And during the benchmark, … value of innodb_max_dirty_pages_pct was set at 90, while the InnoDB log …
Post: DROP TABLE and stalls: Lazy Drop Table in Percona Server and the new fixes in MySQL
June 22, 2012 By 33 Comments
Post: Announcing Percona Server 5.5.27-28.0
August 23, 2012 By 5 Comments
… the upstream MySQL bug #66301. Concurrent INSERT … ON DUPLICATE KEY UPDATE statements on a table with an AUTO_INCREMENT column could result in… default value of innodb_autoinc_lock_mode=1. Bug fixed #1035225 (Alexey Kopytov). Removed error log warnings that occured after enabling innodb_use_sys…
Post: Percona Server 5.1.59-13.0
October 16, 2011 By Leave a Comment
…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
October 16, 2011 By 2 Comments
… 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
September 26, 2007 By 18 Comments
[...] MySQL InnoDB çš„ auto-increment æœƒé€ æˆ INSERT 時使用 table-level lock çš„ bug çµ‚æ–¼ä¿®æ£ (從 2006 年一月就進 MySQL å›žå ±ç³»çµ±çš„ bug)，下個 5.1 的版本 (é 定是 5.1.22) 就會包括在裡é¢ï¼šInnoDB auto-inc scalability fixed。 [...]
