Percona Server 5.7.14-8 is now available

percona server 5.7.14-8Percona announces the GA release of Percona Server 5.7.14-8 on September 21, 2016. Download the latest version from the Percona web site or the Percona Software Repositories.

Based on MySQL 5.7.14, including all the bug fixes in it, Percona Server 5.7.14-8 is the current GA release in the Percona Server 5.7 series. Percona’s provides completely open-source and free software. Find release details in the 5.7.14-8 milestone at Launchpad.

Bugs Fixed:
  • Limiting ld_preload libraries to be loaded from specific directories in mysqld_safe didn’t work correctly for relative paths. Bug fixed #1624247.
  • Fixed possible privilege escalation that could be used when running REPAIR TABLE on a MyISAM table. Bug fixed #1624397.
  • The general query log and slow query log cannot be written to files ending in .ini and .cnf anymore. Bug fixed #1624400.
  • Implemented restrictions on symlinked files (error_log, pid_file) that can’t be used with mysqld_safe. Bug fixed #1624449.

Other bugs fixed: #1553938.

The release notes for Percona Server 5.7.14-8 are available in the online documentation. Please report any bugs on the launchpad bug tracker .

Share this post

Comment (1)

  • Dave Holmes

    Caution with this release it will break replication due to a known upgrade issue in upstream MySQL.

    Given the critical nature of the CVE reports addressed in this release we immediately tested the upgrade on a non-production server taking a feed from production and the replication died looking it lost the master information.

    Upstream bug report: http://bugs.mysql.com/bug.php?id=82765&thanks=3&notify=67

    For information we upgrade the server from 5.7.13-6-log to 5.7.14-8-log and ran MySQL upgrade everything passed.

    2016-09-21T18:40:09.534517Z 0 [ERROR] Info table has a problem with its key field(s). Table ‘mysql.slave_master_info’ expected field #23 to be ‘Channel_name’ but found ‘Tls_version’ instead.
    2016-09-21T18:40:09.534537Z 0 [ERROR] Slave: Failed to create a channel from master info table repository.
    2016-09-21T18:40:09.534565Z 0 [ERROR] Slave: Could not create channel list
    2016-09-21T18:40:09.534572Z 0 [ERROR] Failed to create or recover replication info repositories.
    2016-09-21T18:40:09.534576Z 0 [Note] Check error log for additional messages. You will not be able to start replication until the issue is resolved and the server restarted.
    2016-09-21T18:40:09.553673Z 0 [ERROR] Incorrect definition of table performance_schema.replication_connection_status: expected column ‘RECEIVED_TRANSACTION_SET’ at position 7 to have type longtext, found type text.
    2016-09-21T18:40:09.554945Z 0 [ERROR] Incorrect definition of table performance_schema.replication_group_member_stats: expected column ‘COUNT_TRANSACTIONS_ROWS_VALIDATING’ at position 6, found ‘COUNT_TRANSACTIONS_VALIDATING’.

    There is a workaround on the bug report which does get replication flowing again if you are desperate.

    September 21, 2016 at 3:40 pm

Comments are closed.