You searched for update last row from mysql table - Page 2 of 7

When is MIN(DATE) != MIN(DATE) ?

September 4, 2012 By Ernie Souhrada 5 Comments

Inspiration for this post is courtesy of a friend and former colleague of mine, Greg Youngblood, who pinged me last week with an interesting MySQL puzzle. He was running Percona Server 5.5.21 with a table structure that looks something like this:

CREATE TABLE foo (
 id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,
 uid INT UNSIGNED NOT NULL,
 update_time DATETIME NOT NULL,
 ....
 INDEX `uid` (uid, update_time),
 INDEX `bar` (some_other_columns)
 ....
) ENGINE=InnoDB;

CREATE TABLE foo (

id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,

uid INT UNSIGNED NOT NULL,

update_time DATETIME NOT NULL,

....

INDEX `uid` (uid, update_time),

INDEX `bar` (some_other_columns)

....

) ENGINE=InnoDB;

When he ran this query:

SELECT MIN(update_time) FROM foo WHERE update_time IS NOT NULL AND update_time <> '0000-00-00 00:00:00';

1	SELECT MIN(update_time) FROM foo WHERE update_time IS NOT NULL AND update_time <> '0000-00-00 00:00:00';

The result came back as 2012-06-22 10:28:16. [...]

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

Differences between READ-COMMITTED and REPEATABLE-READ transaction isolation levels

August 28, 2012 By Justin Swanhart 3 Comments

As an instructor with Percona I’m sometimes asked about the differences between the READ COMMITTED and REPEATABLE READ transaction isolation levels. There are a few differences between READ-COMMITTED and REPEATABLE-READ, and they are all related to locking.

Filed Under: Insight for DBAs, MySQL Tagged With: ACID, InnoDB, Locking, Transaction isolation

Full Text Search Webinar Questions Followup

August 24, 2012 By Bill Karwin 5 Comments

I presented a webinar this week to give an overview of several Full Text Search solutions and compare their performance. Even if you missed the webinar, you can register for it, and you’ll be emailed a link to the recording. During my webinar, a number of attendees asked some good questions. Here are their questions and my [...]

Filed Under: Events and Announcements, 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

Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

July 25, 2012 By Frederic Descamps 6 Comments

During the design period of a new cluster, it is always advised to have at least 3 nodes (this is the case with PXC but it’s also the same with PRM). But why and what are the risks ? The goal of having more than 2 nodes, in fact an odd number is recommended in [...]

Filed Under: MySQL, XtraDB Cluster

Impact of memory allocators on MySQL performance

July 5, 2012 By Alexey Stroganov 11 Comments

MySQL server intensively uses dynamic memory allocation so a good choice of memory allocator is quite important for the proper utilization of CPU/RAM resources. Efficient memory allocator should help to improve scalability, increase throughput and keep memory footprint under the control. In this post I’m going to check impact of several memory allocators on the [...]

Filed Under: Benchmarks, MySQL

Find and remove duplicate indexes

June 20, 2012 By Miguel Angel Nieto 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

Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs

February 23, 2012 By Jervin Real 3 Comments

LVM snapshots is one powerful way of taking a consistent backup of your MySQL databases – but did you know that you can now restore directly from a snapshot (and binary logs for point in time recovery) in case of that ‘Oops’ moment? Let me show you quickly how. This howto assumes that you already [...]

Filed Under: Insight for DBAs

The relationship between Innodb Log checkpointing and dirty Buffer pool pages

February 17, 2012 By Jay Janssen 10 Comments

This is a time-honored topic, and there’s no shortage of articles on the topic on this blog. I wanted to write a post trying to condense and clarify those posts, as it has taken me a while to really understand this relationship. Some basic facts Most of us know that writing into Innodb updates buffer [...]

Filed Under: MySQL Tagged With: InnoDB, InnoDB Performance, Tuning

Percona Toolkit 2.0.1 and 1.0.2 released

January 3, 2012 By Baron Schwartz 5 Comments

I’m happy to announce that we’ve released Percona Toolkit 2.0.1, a major new version of our essential DBA toolkit, as well as a minor bugfix update to the old 1.0.x series. You can download it from the project homepage, or install it through our RPM and DEB repositories. Documentation is online (and the 1.0 docs [...]

Filed Under: Events and Announcements, MySQL, Percona Software

When is MIN(DATE) != MIN(DATE) ?

Differences between READ-COMMITTED and REPEATABLE-READ transaction isolation levels

Full Text Search Webinar Questions Followup

Recovery after DROP & CREATE

Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

Impact of memory allocators on MySQL performance

Find and remove duplicate indexes

Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs

The relationship between Innodb Log checkpointing and dirty Buffer pool pages

Percona Toolkit 2.0.1 and 1.0.2 released

Search

Top Searches

Percona Webinars

ABOUT PERCONA

Percona MySQL Training

Percona Careers

SOFTWARE FROM PERCONA

SERVICES FOR MYSQL USERS

ABOUT THIS BLOG AND PERCONA