The Ultimate Guide to High Availability with MariaDB

Optimizer Development

You are viewing an old version of this article. View the current version here.

Notes about Optimizer Development

Contents

  1. mysql-test
    1. InnoDB Estimates are unstable
    2. Run mtr with Optimizer Trace enabled

mysql-test

InnoDB Estimates are unstable

This is caused by background statistics update. It may cause the numbers in EXPLAIN output to be off-by-one. It may also cause different query plans to be picked on different runs (See e.g. MDEV-32901 for details)

On a per-table basis, one can use STATS_AUTO_RECALC=0 as table parameter.

On a per-file basis, one can use this include:

--source mysql-test/include/innodb_stable_estimates.inc

Run mtr with Optimizer Trace enabled

TODO

Comments

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.