MariaDB 10.8.8 Release Notes

Download Release Notes Changelog Overview of 10.8

Release date: 10 May 2023

MariaDB 10.8 is a previous short-term maintenance stable series of MariaDB, maintained until May 2023. It is an evolution of MariaDB 10.7 with several entirely new features.

MariaDB 10.8.8 is a Stable (GA) release.

MariaDB 10.8.8 is the last release of the MariaDB 10.8 release series.

For an overview of MariaDB 10.8 see the What is MariaDB 10.8? page.

Thanks, and enjoy MariaDB!

Notable Items



  • mariadb-backup doesn't utilise innodb-undo-log-directory (if specified as a relative path) during copy-back operation (MDEV-28187)
  • mariabackup issues error messages during InnoDB tablespaces export on partial backup preparing (MDEV-29050)
  • mariadb-backup does not copy Aria logs if aria_log_dir_path is used (MDEV-30968)
  • Race condition between buffer pool flush and log file deletion in mariadb-backup --prepare (MDEV-30860)


  • Fixed a deadlock on parallel slave involving full image Write event on the sequence engine (MDEV-29621)
  • Fixed an attempted out-of-order binlogging error on slave involving ALTER on the sequence engine (MDEV-31077)
  • Corrected non-versioned master to versioned slave replication on no-unique attribute table (MDEV-30430)
  • Mended encrypted binlog master to error out to gtid-mode slave when master could not decrypt a binlog file (MDEV-28798)
  • Refined optimistic parallel slave to error-exit without any hang (MDEV-30780)
  • Ensured SHOW-SLAVE-STATUS is processed on the parallel slave having a necessary mutex always intialized (MDEV-30620)
  • Fixed the slave applier to report a correct error when gtid_slave_pos insert fails for some (engine) reasons (MDEV-31038)
  • Made parallel slave reports in performance schema consistent with that of show-slave-status (MDEV-26071)


  • Split Materialized optimization is improved to re-fill the materialized table only if necessary. The fewer number of table refills is taken into account when choosing query plan, too (MDEV-26301).
  • New optimizer_switch option, hash_join_cardinality, is added. It is off by default. When set to ON, the optimizer will produce tighter bounds for hash join output cardinality. (MDEV-30812)
  • Queries using SELECT DISTINCT some_expression(aggregate_function()) could produce wrong query result. (MDEV-20057)
  • ANALYZE FORMAT=JSON now prints more information about Block Nested Loop joins: block-nl-join element now has r_loops, r_effective_rows and r_other_time_ms fields (MDEV-30806, MDEV-30972).
  • A GROUP BY query with MIN(primary_key) in select list and primary_key<>const in the WHERE could produce wrong result when executed with "Using index for group-by" strategy (MDEV-30605)
  • EXPLAIN could erroneously report that Rowid Filter optimization is used for partitioned tables. Partitioned tables do not support it. (MDEV-30596)
  • A bug in selectivity computations for SINGLE/DOUBLE_PREC_HB histograms could cause wrong estimates to be produced. This could cause the optimizer to pick sub-optimal query plans (MDEV-31067).

Docker Official Image

  • Add replication setup to containers contributed by Md Sahil (MDEV-29762)



For a complete list of changes made in MariaDB 10.8.8, with links to detailed information on each push, see the changelog.


For a full list of contributors to MariaDB 10.8.8, see the MariaDB Foundation release announcement.

Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.