Percona Server for MySQL 5.7.44-56 (2025-11-27)¶

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-56 builds on MySQL 5.7.44 Community Edition,
adding enterprise-grade features and security enhancements from Percona.

Bug fixes¶

The fixes ported to 5.7 are the following:

Bug#38094070: The server could potentially encounter memory access errors when parsing optimizer hints near buffer boundaries. The server now automatically checks buffer boundaries before accessing the next character, preventing potential parsing errors

Bug#37602657: In certain scenarios, secondary indexes on virtual columns can become misaligned with the clustered index data. The fix is when creating update vectors for secondary index updates involving virtual columns, use the field number (field_no) instead of the virtual column position.

Bug#37994397: MySQL’s InnoDB buffer pool, which can be configured across multiple instances and chunks, previously risked silent allocation failures when creating chunk lists for very large buffer pools. The server now explicitly checks and handles allocation failures for the chunk list, ensuring robust memory management during buffer pool initialization.

Bug#37792010: In MySQL 5.7, full-text search (FTS) configuration table columns lacked proper type initialization, which could potentially cause a server crash when concurrent queries accessed the INFORMATION_SCHEMA.INNODB_LOCKS table under specific rare conditions. The fix ensures these internal VARCHAR columns are initialized with valid type information, preventing potential crashes during concurrent table access.

Additional Resources¶

Last update: 2025-11-27