May 23, 2013

How to recover table structure from InnoDB dictionary

April 22, 2013 By 4 Comments

To recover a dropped or corrupt table with Percona Data Recovery Tool for InnoDB you need two things: media with records(ibdata1, *.ibd, disk image, etc.) and a table structure. Indeed, there is no information about the table structure in an InnoDB page. Normally we either recover the structure from .frm files or take it from [...]

Filed Under: Insight for DBAs, MySQL Tagged With: , , , , , ,

Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

April 17, 2013 By 2 Comments

Percona is glad to announce the release of Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL on April 17, 2013. Binaries are available from the downloads area or from our software repositories. New Features: Percona XtraDB Cluster has implemented initial implementation of weighted quorum. Weight for node can be assigned via pc.weight option in the wsrep_provider_options variable. [...]

Filed Under: MySQL, XtraDB Cluster Tagged With: , ,

MySQL optimizer: ANALYZE TABLE and Waiting for table flush

February 27, 2013 By 3 Comments

The MySQL optimizer makes the decision of what execution plan to use based on the information provided by the storage engines. That information is not accurate in some engines like InnoDB and they are based in statistics calculations therefore sometimes some tune is needed. In InnoDB these statistics are calculated automatically, check the following blog [...]

Filed Under: MySQL Tagged With: , , , ,

Sphinx search performance optimization: attribute-based filters

January 15, 2013 By 9 Comments

One of the most common causes of a poor Sphinx search performance I find our customers face is misuse of search filters. In this article I will cover how Sphinx attributes (which are normally used for filtering) work, when they are a good idea to use and what to do when they are not, but [...]

Filed Under: Insight for Developers, MySQL Tagged With: , ,

The Optimization That (Often) Isn’t: Index Merge Intersection

December 14, 2012 By 6 Comments

Prior to version 5.0, MySQL could only use one index per table in a given query without any exceptions; folks that didn’t understand this limitation would often have tables with lots of single-column indexes on columns which commonly appeared in their WHERE clauses, and they’d wonder why the EXPLAIN plan for a given SELECT would [...]

Filed Under: Insight for DBAs, Insight for Developers, MySQL

Edge-case behavior of INSERT…ODKU

October 27, 2012 By 6 Comments

A few weeks back, I was working on a customer issue wherein they were observing database performance that dropped through the floor (to the point of an outage) roughly every 4 weeks or so. Nothing special about the environment, the hardware, or the queries; really, the majority of the database was a single table with [...]

Filed Under: Insight for DBAs, Insight for Developers, MySQL

Logging Foreign Key errors

September 27, 2012 By Leave a Comment

In the last blog post I wrote about how to log deadlock errors using Percona Toolkit. Foreign key errors have the same problems. InnoDB only logs the last error in the output of SHOW ENGINE INNODB STATUS, so we need another similar tool in order to have historical data. pt-fk-error-logger This is a tool very [...]

Filed Under: MySQL

MySQL Indexing Best Practices: Webinar Questions Followup

August 16, 2012 By 4 Comments

I had a lot of questions on my MySQL Indexing: Best Practices Webinar (both recording and slides are available now) We had lots of questions. I did not have time to answer some and others are better answered in writing anyway. Q: One developer on our team wants to replace longish (25-30) indexed varchars with [...]

Filed Under: Insight for DBAs, MySQL

On Character Sets and Disappearing Tables

June 21, 2012 By 1 Comment

The MySQL manual tells us that regardless of whether or not we use “SET FOREIGN_KEY_CHECKS=0″ before making schema changes, InnoDB will not allow a column referenced by a foreign key constraint to be modified in such a way that the foreign key will reference a column with a mismatched data type. For instance, if we [...]

Filed Under: Insight for DBAs, MySQL

Find and remove duplicate indexes

June 20, 2012 By 9 Comments

Having duplicate keys in our schemas can hurt the performance of our database: They make the optimizer phase slower because MySQL needs to examine more query plans. The storage engine needs to maintain, calculate and update more index statistics DML and even read queries can be slower because MySQL needs update fetch more data to [...]

Filed Under: Insight for DBAs, Insight for Developers, MySQL, Percona Software
« Older Posts