May 25, 2012

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

rows in set (0.00 sec) As you can see FLUSH TABLES WITH READ LOCK is waiting for that very nasty “full join” selecthave similar option. This option can be especially helpful when backing up data

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

have the following query executed on the InnoDB table: SELECT non…table, the number of these point primary key lookups will be depend on the number of rows that…76882 102672 76832 Innodb_data_read 1.84G 1…in query times between MySQL 5.5 and MySQL 5.6/MariaDB 5.5 This is another area of improvement in

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in… new optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take…

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

MySQL always uses Nested Loop Join to join two or more tables. What this means is that, select rows from first table participating inin my previous post) to lookup the rows in table2. So this means that we haveAnother thing that is important to know is that

Post: InnoDB's gap locks

that table. This makes reads consistent and therefore makes the replication between servers consistent. If you execute SELECTrow lock(s), undo log entries 1 MySQL thread id 3, OS thread handle 0x7f84a78ba700, query id 163 localhost msandbox TABLE LOCK table

Post: How to recover deleted rows from an InnoDB Tablespace

mysql (information_schema) > SELECT ROW_FORMAT from TABLES WHERE TABLE_SCHEMA=’employees’ AND TABLE_NAME=’salaries’; +————+ | ROW_FORMAT | +————+ | Compact | +————+ ~/recovery-tool# ./page_parser -5 -f data

Post: Using Flexviews - part two, change data capture

in one of the following ways: Timestamps (usually more than one) to identify rows that haverow to process SBR changes from a MySQL master. I’ll talk more about that in anothertable is `test`.`demo`. mysql> select * from flexviews.test_demo\G *************************** 1. row

Post: Flexviews - part 3 - improving query performance using materialized views

in the data dictionary: mysql> select * from flexviews.mview_table where mview_id= flexviews.get_id(‘demo’,'dashboard_customer_sales’)\G *************************** 1. row *************************** mview_table

Post: Recovering Innodb table Corruption

rows affected (0.91 sec) Records: 229376 Duplicates: 0 Warnings: 0 Now you got all your data in MyISAM table so all you havemysql> select max(id) from test2; +———+ | max(id) | +———+ | 220 | +———+ 1 row in set (0.00 sec) mysql> insert ignore into test2 select

Post: MySQL-Memcached or NOSQL Tokyo Tyrant - part 1

data from that row and replace the stored contents on disk C.) Use the data from that row to lookup up a row in another tablein MySQL coupled with the still large # of reads takes its toll. Another place where I have seen this kill clients is in apps that