You searched for mysql temp tables variable

Is Synchronous Replication right for your app?

May 14, 2013 By Jay Janssen 17 Comments

I talk with lot of people who are really interested in Percona XtraDB Cluster (PXC) and mostly they are interested in PXC as a high-availability solution. But, what they tend not to think too much about is if moving from async to synchronous replication is right for their application or not. Facts about Galera replication [...]

Filed Under: MySQL, Percona Software, XtraDB Cluster Tagged With: async, Galera replication, hotspots, Jay Janssen, Percona XtraDB Cluster, pxc, Synchronous Replication

Rotating MySQL slow logs safely

April 18, 2013 By Peter Boros 7 Comments

This blog post is part two of two. Like part one, published Wednesday, this is a cross-post from Groupon’s engineering blog. Thanks again to Kyle Oppenheim at Groupon. And one more reminder that I’ll be at the Percona Live MySQL Conference and Expo next week in Santa Clara, California so look for me there. You [...]

Filed Under: Insight for DBAs, MySQL Tagged With: copytruncate, FLUSH LOGS, Groupon, Kyle Oppenheim, Logrotate, MySQL slow logs, no copytruncate, Peter Boros

MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

March 11, 2013 By Justin Swanhart 7 Comments

So far most of the benchmarks posted about MySQL 5.6 use the sysbench OLTP workload. I wanted to test a set of queries which, unlike sysbench, utilize joins. I also wanted an easily reproducible set of data which is more rich than the simple sysbench table. The Star Schema Benchmark (SSB) seems ideal for this. [...]

Filed Under: MySQL Tagged With: InnoDB plugin, Justin Swanhart, MySQL 5.5, MySQL 5.6, Star Schema Benchmark (SSB), sysbench

InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

March 4, 2013 By Ernie Souhrada 7 Comments

This is part 2 in a 3 part series. In part 1, we took a quick look at some initial configuration of InnoDB full-text search and discovered a little bit of quirky behavior; here, we are going to run some queries and compare the result sets. Our hope is that the one of two things [...]

Filed Under: Insight for DBAs, Insight for Developers, MySQL Tagged With: Ernie Souhrada, FTS, FullText Search, InnoDB, MyISAM, MySQL 5.6

Announcing Percona XtraDB Cluster 5.5.29-23.7.1

January 30, 2013 By Hrvoje Matijakovic 8 Comments

Percona is glad to announce the release of Percona XtraDB Cluster on January 30th, 2013. Binaries are available from downloads area or from our software repositories. Bugs fixed: In some cases when node is recovered variable threads_running would become huge. Bug fixed #1040108 (Teemu Ollakka). Variable wsrep_defaults_file would be set up to the value in [...]

Filed Under: Events and Announcements, MySQL, Percona Software, XtraDB Cluster

MySQL Wish for 2013 – Better Memory Accounting

December 31, 2012 By Peter Zaitsev 6 Comments

With Performance Schema improvements in MySQL 5.6 I think we’re in the good shape with insight on what is causing performance bottlenecks as well as where CPU resources are spent. (Performance Schema does not accounts CPU usage directly but it is something which can be relatively easily derived from wait and stage information). Where we’re [...]

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

Auditing login attempts in MySQL

December 28, 2012 By Miguel Angel Nieto 4 Comments

This is a recurrent question made by our MySQL Support customers: How can I audit the login attempts in MySQL? Logging all the attempts or just the failed ones is a very important task on some scenarios. Unfortunately there are not too many audit capabilities in MySQL Community so the first option to audit MySQL’s [...]

Filed Under: MySQL Tagged With: audit, login, MySQL Support

Announcing Percona Server 5.6.6-60.1 Alpha

September 13, 2012 By Stewart Smith 2 Comments

Percona is glad to announce the ALPHA release of Percona Server 5.6.6-60.1 on September 14, 2012 (Downloads are available here and from the EXPERIMENTAL Percona Software Repositories, although currently only for RHEL/CentOS as we are working on ensuring compatibility with our Debian/Ubuntu packages). Based on MySQL 5.6.6, including all the bug fixes in it, Percona Server 5.6.6-60.1 is the second ALPHA release in [...]

Filed Under: Percona Software

How to obtain the “LES” (Last Executed Statement) from an Optimized Core Dump?

September 9, 2012 By Roel Van de Paar 9 Comments

Ever ran into a situation where you saw “some important variable you really needed to know about=<optimized out>” while debugging?

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

Recovery after DROP & CREATE

August 22, 2012 By Aleksandr Kuzminsky 1 Comment

In a very popular data loss scenario a table is dropped and empty one is created with the same name. This is because mysqldump in many cases generates the “DROP TABLE” instruction before the “CREATE TABLE”:

DROP TABLE IF EXISTS `actor`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `actor` (
  `actor_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,
  `first_name` varchar(45) NOT NULL,
  `last_name` varchar(45) NOT NULL,
  `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`actor_id`),
  KEY `idx_actor_last_name` (`last_name`)
) ENGINE=InnoDB AUTO_INCREMENT=201 DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;

DROP TABLE IF EXISTS `actor`;

/*!40101 SET @saved_cs_client = @@character_set_client */;

/*!40101 SET character_set_client = utf8 */;

CREATE TABLE `actor` (

`actor_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,

`first_name` varchar(45) NOT NULL,

`last_name` varchar(45) NOT NULL,

`last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

PRIMARY KEY (`actor_id`),

KEY `idx_actor_last_name` (`last_name`)

) ENGINE=InnoDB AUTO_INCREMENT=201 DEFAULT CHARSET=utf8;

/*!40101 SET character_set_client = @saved_cs_client */;

If there were no subsequent CREATE TABLE the recovery would be trivial. Index_id of the PRIMARY index of [...]

Filed Under: MySQL Tagged With: drop table, InnoDB, Recovery

Is Synchronous Replication right for your app?

Rotating MySQL slow logs safely

MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

Announcing Percona XtraDB Cluster 5.5.29-23.7.1

MySQL Wish for 2013 – Better Memory Accounting

Announcing Percona Server 5.6.6-60.1 Alpha

How to obtain the “LES” (Last Executed Statement) from an Optimized Core Dump?

Recovery after DROP & CREATE

Search

Top Searches

Percona Webinars

ABOUT PERCONA

Percona MySQL Training

Percona Careers

SOFTWARE FROM PERCONA

SERVICES FOR MYSQL USERS

ABOUT THIS BLOG AND PERCONA