Released on June 8, 2011 (Downloads are available here and from the Percona Software Repositories.
Percona Server 5.1.57-12.8 is now the current stable release in the 5.1 series. It is is based on MySQL 5.1.57.
pwrite(). Bug Fixed: LaunchPad: #764395 / MySQL bug #60788 (A. Kopytov)innodb_use_purge_threads has been corrected to 32 (maximum number of parallel threads in a parallelized operation). The innodb_purge_thread patch accepted a value up to 64 for the innodb_use_purge_thread variable, leading to an assertion failure for greater than the actual maximum. Bug Fixed: #755017 (L. Biveinis)
For more information, please see the following links:
Ok, thanks, that makes sense. Google finds lots of hits on “lustre” and “EINTR”
@Kristian – our customer was running into this on Lustre file system
Was hoping for a real life upgrade, guess I could build a test enviroment. But there’s no place like live =)
@dan Here is article about upgrading MySQL: http://www.mysqlperformanceblog.com/2010/01/05/upgrading-mysql/
Is there a way to reproduce Bug#60788, receiving signal on pwrite()?
Normally, it is not possible to get an interrupt while writing to a block device (eg. disk), only on a pipe or socket or similar. The only exception I can think of is if one would put InnoDB data files on NFS mounted with the “intr” option. Is this what happened in this bug?
I would be very interested in learning under which circumstances it is possible to get an interrupt in pwrite() on a block device.
How safe would it be to upgrade from 5.1 to 5.5 using the apt repo?
Corrected
Thanks!
“The authors of the plugins used have been corrected.”
You’ve been bad, very bad.
Oh you mean the list of authors has been corrected
The “series” are a way of distinguishing on which version of MySQL the server is based on. The 5.1 serie is based on MySQL 5.1 and 5.5 is based on MySQL 5.5.
What is of difference with 5.1 and 5.5 series?