Personal blog of Yzmir Ramirez

Percona Server version 5.6.13-60.5

Percona is glad to announce the third Release Candidate of Percona Server 5.6.13-60.5 (downloads are available here and from the Percona Software Repositories).

The final release is almost ready. Thank you to everyone who has been testing and filing bugs. You’ve been a big help and we can’t wait for you to see the fantastic results. Currently the team is doing the final polish and testing on Percona Server 5.6 so look for the GA later this month.

Have you been evaluating or using Percona Server 5.6? What new features in Percona Server can you not live without? We’d like to hear about your experiences and the results you’ve seen in your applications. Share your thoughts in the comments below or send us a message.

Based on the recently released MySQL 5.6.13, including all the bug fixes in it, Percona Server 5.6.13-60.5 is the third RC release in the Percona Server 5.6 series. Percona Server is an enhanced, drop-in MySQL replacement. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.6.13-60.5 milestone at Launchpad.

Ported Features:

• Fixed Size for the Read Ahead Area has been ported from Percona Server 5.5

Bugs Fixed:

• If binary log was enabled, Fake Changes transactions were binlogged. This could lead to data corruption issues with deeper replication topologies. Bug fixed #1190580.
• Querying INFORMATION_SCHEMA.PARTITIONS could cause key distribution statistics for partitioned tables to be reset to those corresponding to the last partition. Fixed the upstream bug #69179. Bug fixed #1192354.
• Changes made to the RPM scripts for previous Percona Server version caused installer to fail if there were different datadir options in multiple configuration files. Bug fixed #1201036.
• Fixed the upstream bug #42415 that would cause UPDATE/DELETE statements with the LIMIT clause to be unsafe for Statement Based Replication even when ORDER BY primary key was present. Fixed by implementing an algorithm to do more elaborate analysis on the nature of the query to determine whether the query will cause uncertainty for replication or not. Bug fixed #1132194.
• When an upgrade was performed between major versions (e.g. by uninstalling a 5.1 RPM and then installing a 5.5 one), mysql_install_db was still called on the existing data directory which lead to re-creation of the test database. Bug fixed #1169522.
• Fixed the upstream bug #69639 which caused compile errors for Percona Server with DTrace version Sun D 1.11 provided by recent SmartOS versions. Bug fixed #1196460.
• Fixed a regression introduced in Percona Server 5.6.12-60.4, where server wouldn’t be able to start if Atomic write support for Fusion-io devices was enabled. Bug fixed #1214735.

Other bugs fixed: bug fixed #1188162, bug fixed #1203308 and bug fixed #1189743.

Release notes for Percona Server for MySQL 5.6.13-60.5 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

The post Percona Server 5.6.13-60.5 third Release Candidate is now available appeared first on MySQL Performance Blog.

Percona Server for MySQL version 5.1.69-14.7

Percona is glad to announce the release of Percona Server 5.1.69-14.7 on June 10, 2013. A drop in replacement for MySQL, downloads are available  here and from the Percona Software Repositories. Based on MySQL 5.1.69, this release will include all the bug fixes in it. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.1.69-14.7 milestone at Launchpad.

Bugs Fixed:

• In Ubuntu Precise libmysqlclient18 package was chosen from the distribution’s repository instead of Percona’s which could lead to package conflicts. Bug fixed #1174271.
• Fixed the RPM Percona-Server-shared-compat package naming issue that could lead to unresolved package dependencies when installing Percona Server 5.1. Bug fixed #893860.
• The log tracker thread was unaware of the situation when the oldest untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser or bad changed page data. Bug fixed #1108613.
• Percona Server wouldn’t start if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949.
• Fixed the RPM package dependencies for different major versions of Percona Server. Bug fixed #1167109.
• Fixed the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. This bug fix comes originally from MariaDB (see MDEV-3915). Bug fixed #1172090.
• OpenSSL libraries were not found in 32-bit builds due to a typo. Bug fixed #1175447.
• Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed #1179974.
• Server would crash if an INNODB_CHANGED_PAGES query is issued that has an empty LSN range and thus does not need to read any bitmap files. Bug fixed #1184427.
• Incorrect schema definition for the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS, THREAD_STATISTICS, and USER_STATISTICS) led to the maximum counter values being limited to 32-bit signed integers. Fixed so that these values can be 64-bit unsigned integers now. Bug fixed #714925.
• mysql_set_permission was failing on Debian due to missing libdbd-mysql-perl package. Fixed by adding the package dependency. Bug fixed #1003776.
• XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699.
• Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir variable didn’t have the path separator at the end. Bug fixed #1181887.
• A warning is now returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040.
• Fixed the upstream bug #69379 which caused MySQL clients to return bogus error number for host-not-found errors on Ubuntu 13.04. Bug fixed #1186690.
• Under very rare circumstances, deleting a zero-size bitmap file at the right moment would make server stop with an I/O error if changed page tracking is enabled. Bug fixed #1184517.
• The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t running. Bug fixed #1185304.

Other bug fixes: bug fixed #1174346, bug fixed #1160951, bug fixed #1079688, bug fixed #1132412, bug fixed #1153651.

Release notes for Percona Server for MySQL 5.1.69-17.4 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

The post Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL appeared first on MySQL Performance Blog.

Percona Server for MySQL version 5.1.68-14.5

Percona is glad to announce the release of Percona Server for MySQL 5.1.68 -14.5 on March 15, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.68, including all the bug fixes in it, Percona Server 5.1.68 -14.5 is now the current stable release in the 5.1 series. All of Percona‘s software is open source and free, all the details of the release can be found in the 5.1.68-14.5 milestone at Launchpad.

This release contains no further bug fixes than what is included in the previous Percona Server release and MySQL 5.1.68.

Bugs can be reported on the launchpad bug tracker.

More on Percona Server for MySQL
A free, open-source solution, Percona Server for MySQL is an enhanced drop-in replacement for MySQL, offering breakthrough performance, scalability, features, and instrumentation. Self-tuning algorithms and support for extremely high-performance hardware make it the clear choice for organizations that demand excellent performance and reliability from their MySQL database server.  Compare Percona Server to MySQL.

Performance
Percona Server’s performance is exceptional. Not only is it faster, but in benchmarking, it is more stable and consistent. Our research into server internals and our Six-Sigma-like focus on quality of service have resulted in the industry’s most predictable response times and throughput. Standard MySQL suffers from complete lockups due to checkpointing and furious flushing to disk.

Additional Resources
> Commercial Support
> Documentation
> White Papers
> Case Studies
> Community Discussion Forum

The post Announcing Percona Server for MySQL 5.1.68 -14.5 appeared first on MySQL Performance Blog.