May 25, 2012

Post: MariaDB 5.3 is released as GA!

…. MariaDB 5.3 isn’t the only exciting thing, however. MariaDB 5.3 is based on MySQL 5.1, but MariaDB 5.5 will be based on MySQL 5.5… like less lock contention, better diagnostics, improvements to partitioning, and the addition of multiple InnoDB buffer pools. Best of all, MariaDB 5.5 might…

Post: InnoDB's gap locks

… no need to create locks to prevent that from happening. 2- innodb_locks_unsafe_for_binlog = 1. Disables the gap locks except for foreign-key… locks can be different. In the following link there is a good source of information: http://dev.mysql.com/doc/refman/5.1/en/innodb-locks-set.html. Conclusion MySQL uses REPEATABLE READ as the default isolation level so it needs to lock

Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

MySQL 5.5 FLUSH TABLES WITH READ LOCK does not work as optimally as you could think it works. Even though with general lock…0 | 1 | +——-+——+———–+———-+————+——+——————————+——————————+———–+—————+———–+ 5Innodb

Post: Troubleshooting MySQL Memory Usage

…problems with MySQL 5.5 with addition …mysql> select * from information_schema.global_temporary_tables \G *************************** 1. row *************************** SESSION_ID: 7234 TABLE_SCHEMA: test TABLE_NAME: my ENGINE: InnoDB… 294352 (82672 + 211680) Lock system 318875832 (318747272 + 128560…

Comment: Innodb Performance Optimization Basics

… are in InnoDB with MySQL 5 and RHEL 5. Its a 32 bit machine with 12 Gb RAM. The imp param for InnoDB are [root… = 2000M innodb_additional_mem_pool_size = 2M innodb_log_file_size = 65M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 A count command with approx 3 million records is taking too long and all my transactions are locked

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

mysql from 5.1.22 change autoincrement mod http://dev.mysql.com/doc/refman/5.1/en/innodb-auto-increment-handling.html I have the same problem. 1… before 5.1.22 # =1 is default value – consecutive lock mode # =2 is interleaved lock mode , i don’t investigate what it do innodb_autoinc_lock_mode…

Comment: Best kept MySQLDump Secret

I did the same test on windows2003 mysql 5.5.15 while mysqldump is going , alter table was BLOCKED! Eventually …` char(1) DEFAULT ” ) ENGINE=InnoDB DEFAULT CHARSET=utf8; /*!40101 SET character_set_client = @saved_cs_client */; — – Dumping data for table `z` — LOCK TABLES…

Post: Percona Server 5.1.58-12.9

MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1…for the deprecated options (innodb_buffer_pool_shm_key and innodb_buffer_pool_shm_checksum…in some scenarios due to insufficient locking. Fixed by introducing a new …

Post: Percona Server 5.1.59-13.0

…Repositories). Based on MySQL 5.1.59, including all the bug fixes in it, Percona Server 5.1.59-13.0…be found in the 5.1.59-13.0 milestone at Launchpad. New Features InnoDB Fake Changes When restarting… makes prefetch simple but has high overhead from locking rows only to undo changes at rollback. …

Post: MySQL Users Conference - Innodb

… in MySQL 5.2 or even MySQL 5.1. I surely would like to see it sooner at least in more flexible community version. Relaxing Locks… when Innodb was first implemented. Many other transactional Storage Engines do not have the problems because they target at least MySQL 5.1 with… benchmarks stress testing other areas in Innodb than buffer-pool which had it locking relaxed in latest MySQL 5.0 Hopefully the patches he…