Skip to content

Percona Server for MySQL 5.7.44-53 (2025-02-05)

This release is part of Percona’s MySQL 5.7 Post-End-of-Life (EOL) support
program. It provides critical updates and ensures stability for businesses
relying on MySQL 5.7 beyond its official EOL.

  • Paying customers can access the full release, including pre-compiled
    binaries, through the private repository.

  • Community members can build the release from publicly available source
    code, which is released quarterly.

Upgrading to MySQL 8.0 is recommended, but support for MySQL 5.7 will continue.

Release Information

Percona Server for MySQL 5.7.44-53 builds on MySQL 5.7.44 Community Edition,
adding enterprise-grade features and security enhancements from Percona.

Bug fixes

  • Bug#36234681: A DELETE operation on a table with a self-referential foreign key constraint involving a full-text index triggered an assertion.

  • Bug#37189985: Using ALTER TABLE ... ALGORITHM=INPLACE may result a in server exits and corrupt spatial indexes when used on a table with an auto-increment column.

  • Bug#33691659: Performing ON DELETE CASCADE on a table with a secondary index on a generated column may cause a server exit in innobase_get_computed_value.

  • Bug#33327093: An operation attempted to update a virtual column while building an update node for a child table and caused an assertion failure in row_MySQL_pad_col.

  • Bug#34574604: The virtual column information for a row containing an externally stored BLOB was not always logged during an UPDATE operation and may cause permanent corruptions.

  • Bug#36593235: A subquery containing an aggregate function WITH ROLLUP which was part of a row value comparator was not always processed correctly.

  • Bug#37068527: When the server is compiled with XCode 16, a bad comparator caused a server exit during the mysqld initialization.

  • Bug#37132323: The server exited because the database cache wasn’t flushed when a user was dropped.

  • Bug#37063288: The server exited because AppArmor denied access to the file /proc/<pid>/task/<thread_id>/mem which is needed to generate a stack trace.

  • Bug#36615714: Fixes a buffer overrun in my_print_help.

  • Bug#30875669: The mysql client now allows to send a query containing a number sign or double dash in an optimizer hint comment.

  • Bug#36879147: Adds support to 64 bit FTS_DOC_ID doc ids for InnoDB FULLTEXT index where earlier, they were imprecisely limited to the maximum unsigned 32-bit value.

Additional Resources

Last update: 2025-02-03