EmergencyEMERGENCY? Get 24/7 Help Now!

Percona Server 5.6.16-64.2 is now available

 | March 25, 2014 |  Posted In: Events and Announcements, Percona Server, Percona Software

PREVIOUS POST
NEXT POST
Percona Server version 5.6.16-64.2
Percona Server version 5.6.16-64.2

Percona is glad to announce the release of Percona Server 5.6.16-64.2 on March 25th, 2014. Downloads are available here and from the Percona Software Repositories.

Based on MySQL 5.6.16, including all the bug fixes in it, Percona Server 5.6.16-64.1 is the current GA release in the Percona Server 5.6 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.6.16-64.2 milestone at Launchpad.

Bugs Fixed:

  • The upgrade to Percona Server 5.6.16-64.1 would silently comment out any options in my.cnf that have paths specified that contain share/mysql. Bug fixed #1293867.
  • Percona Server could fail to start after upgrade if the lc-messages-dir option was set in the my.cnf configuration file. Bug fixed #1294067.
  • Dependency on mysql-common package, introduced in Percona Server 5.6.16-64.0 could lead to wrongly chosen packages for upgrade, spurious removes and installs with some combination of packages installed which use the mysql libraries. Bug fixed #1294211.
  • These three bugs were fixed by removing the dependency on mysql-common package.
  • Percona Toolkit UDFs were missing from Debian/Ubuntu packages, this regression was introduced in Percona Server 5.6.16-64.0. Bug fixed #1296416.
  • Percona Server installer will create the symlinks from libmysqlclient to libperconaserverclient during the installation on CentOS. This was implemented in order to provide the backwards compatibility after the libmysqlclient library has been renamed to libperconaserverclient .

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

PREVIOUS POST
NEXT POST

One Comment

  • I realize it’s possible to fix the “libperconaserverclient.so versus libmysqlclient.so problem” at compile time by patching some of the source files prior to compilation, but I am still reiterating my request that Percona make this a compile-time configuration option.

    Percona Server is billed as a “drop-in” replacement for Oracle MySQL. When I build from source, I need the resulting binaries, libraries, and support files to be named exactly as they are in a full Oracle MySQL installation. I understand that some Linux distros split the client-side and server-side components, but others (such as Slackware) do not.

    There has got to be a better way of supporting all distros – whether MySQL is monolithic or split into client-server components. Making the choice configurable when building the package would go a long way toward alleviating the problems we are seeing.

    Thank you for your consideration.

Leave a Reply

 
 

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.

No, thank you. Please do not ask me again.