Percona is glad to announce the release of Percona Server for MySQL version 5.1.67-14.4 on March 8, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.67, including all the bug fixes in it, Percona Server 5.1.67-14.4 is now the current stable release in the 5.1 series. All of Percona‘s software is open-source and free, all the details [...]
Announcing Percona Server for MySQL version 5.5.29-30.0
February 26, 2013 By Leave a Comment
Percona is glad to announce the release of Percona Server for MySQL version 5.5.29-30.0 on February 26th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.29, including all the bug fixes in it, Percona Server 5.5.29-30.0 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details [...]
Adventures in archiving
February 11, 2013 By 16 Comments
One of our Remote DBA service clients recently had an issue with size on disk for a particular table; in short this table was some 25 million rows of application audit data with an on disk size of 345GB recorded solely for the purposes of debugging which may or may not occur. Faced with the task of [...]
Data compression in InnoDB for text and blob fields
May 30, 2012 By 2 Comments
Have you wanted to compress only certain types of columns in a table while leaving other columns uncompressed? While working on a customer case this week I saw an interesting problem where a table had many heavily utilized TEXT fields with some read queries exceeding 500MB (!!), and stored in a 100GB table. In this [...]
Troubleshooting MySQL Memory Usage
March 21, 2012 By 5 Comments
One of the most painful troubleshooting tasks with MySQL is troubleshooting memory usage. The problem usually starts like this – you have configured MySQL to use reasonable global buffers, such as innodb_buffer_size, key_buffer_size etc, you have reasonable amount of connections but yet MySQL takes much more memory than you would expect, causing swapping or other [...]
Identifying the load with the help of pt-query-digest and Percona Server
December 29, 2011 By 3 Comments
Overview Profiling, analyzing and then fixing queries is likely the most oft-repeated part of a job of a DBA and one that keeps evolving, as new features are added to the application new queries pop up that need to be analyzed and fixed. And there are not too many tools out there that can make [...]
Bug#12704861
November 20, 2011 By 1 Comment
As Mark pointed out, there isn’t a lot of detail in the release notes about what could potentially be a very serious problem that is fixed in MySQL 5.1.60. I’ll repeat here the full documentation from the release notes: “InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise [...]
Innodb undo segment size and transaction isolation
January 12, 2011 By 3 Comments
You might know if you have long running transactions you’re risking having a lot of “garbage” accumulated in undo segment size which can cause performance degradation as well as increased disk space usage. Long transactions can also be bad for other reasons such as taking row level locks which will prevent other transactions for execution, [...]
Percona Server 5.1.50-rel12.1
October 14, 2010 By 2 Comments
Dear Community, Percona Server version 5.1.50-rel12.1 RC is now available for download. Functionality Added or Changed Percona Server 5.1.50-rel12.1 is now based on MySQL 5.1.50. New Features Added: innodb_lru_dump_restore – Implemented automatic dumping of the buffer pool at specified intervals. innodb_buffer_pool_shm – Implemented option ”innodb_buffer_pool_shm_checksum”; when enabled, shared memory buffer pool is checksum validated. This [...]
Blob Storage in Innodb
February 9, 2010 By 13 Comments
I’m running in this misconception second time in a week or so, so it is time to blog about it. How blobs are stored in Innodb ? This depends on 3 factors. Blob size; Full row size and Innodb row format. But before we look into how BLOBs are really stored lets see what misconception [...]
