Skip to content

Rate this page
Thanks for your feedback
Thank you! The feedback has been submitted.

For help, click the link below to get free database assistance or contact our experts for personalized support.

Percona Server for MySQL 8.4.8-8 (2025-03-12)

Get started with Quickstart Guide for Percona Server for MySQL.

Percona Server for MySQL 8.4.8-8 includes all the features and bug fixes available in the MySQL 8.4.8 Community Edition in addition to enterprise-grade features developed by Percona.

Release highlights

MySQL 8.4.8

Improvements and bug fixes introduced by Oracle for MySQL 8.4.8 and included in Percona Server for MySQL are the following:

  • The warning associated with redo logging being disabled is no longer present, as the underlying condition that triggered the warning has been eliminated. (Bug #37645185)

  • A problem affecting the handling of large insert operations has been corrected, improving stability during bulk data loads. (Bug #38208188)

  • An error that could arise when running certain SQL statements has been resolved. (Bug #38573285)

  • Issues encountered when generating table definitions via SHOW CREATE TABLE have been fixed. (Bug #38448700)

  • Bug #38298692 was addressed as part of the same fix set as Bug #38448700, resolving related inconsistencies in table metadata handling. (Bug #38298692)

  • Performance regressions affecting queries that rely on regular expression matching have been corrected. (Bug #114056, Bug #36326728)

  • The bundled OpenSSL dependency has been updated, addressing the issue tracked under Bug #38632932. (Bug #38632932)

  • A concurrency flaw in InnoDB that could occur when executing SQL through the que_eval_sql interface has been removed. (Bug #118705, Bug #38310595)

  • A timing issue that allowed binary logs to be removed before persisted expiration settings were fully applied has been fixed. (Bug #38554467)

  • A fault affecting clustered environments, where multiple instances could lose connectivity under specific conditions, has been corrected. (Bug #38380392)

  • Several defects that prevented connections from closing properly when using the Thread Pool have been resolved. (Bug #38170188, Bug #36782728, Bug #38549372)

  • An issue that caused gaps in GTID sequences when the replica_skip_errors option was enabled has been fixed. (Bug #28590993)

Find the complete list of bug fixes and changes in the MySQL 8.4.8 release notes .

Bug Fixes

  • PS-9828: The Audit Log Filter could crash when audit_log_filter.file pointed to a non-existent directory.

  • PS-10229: The audit_log_filter_remove_filter failed after upgrading from Percona Server for MySQL 8.0 to 8.4.6 due to an index being renamed from filter_name to filtername. The issue resulted in the error: ERROR: Failed to remove filter from users table.

  • PS-10232: MySQL 8.0.40 and later could be about 2–3 times slower than 8.0.39 in a particular index scan scenario.

  • PS-10260: Expanded Fast Index Creation could fail with partitioned tables.

  • PS-10287: A table definition mismatch between MyRocks and the data dictionary after a crash could cause a crash or assertion failures.

  • PS-10332: MySQL terminated with signal SIGABRT when an invalid value was specified for audit-log-filter.compression.

  • PS-10345: The Audit Log Filter could crash when the definition passed to audit_log_filter_set_filter() contained invalid data replacement fields.

  • PS-10347: The AuditJsonHandler used by the audit_log_read UDF could return malformed JSON.

  • PS-10383: The MeCab plugin did not enforce phrase adjacency for quoted phrase search in BOOLEAN MODE.

  • PS-10387: The audit_log_read() function ignored max_array_length and had pagination issues.

  • PS-10446: Back-ported the fix for Bug #118512 (missing semi-join condition causes incorrect result) to 8.4.

  • PS-10447: Back-ported the fix for Bug #119606 (assertion failure in item_func.cc:3937) to 8.4.

  • PS-10545: MySQL Test Run (MTR) --only-big-test incorrectly skipped tests that included both big_test.inc and no_valgrind_without_big.inc.

  • PS-10591: On systems running OpenSSL 3.4 or later (for example, Debian Trixie and Oracle Linux 10), the use of SHAKE128 and SHAKE256 resulted in an assertion failure. Because SHAKE algorithms are extendable-output functions (XOFs), EVP_MD_CTX_size() returned 0, which triggered assert(digest_size > 0) in finalize(). The implementation was updated to properly handle XOF algorithms and to use EVP_DigestFinalXOF() instead of EVP_DigestFinal_ex() for finalizing XOF digests.

Additional resources