go-v.orgdoi

MariaDB and MySQL — what statistics optimizer needs

Golubchik, Sergei · TIB AV-Portal · 2019

  • DOI 10.5446/44404
  • Publisher Technische Informationsbibliothek (TIB)
  • Type other
  • Issued 2019

Not cached yet. This record was fetched live for this request and is stored after the lookup. Reopening the page should serve the cached copy.

TIB AV-Portal · Technische Informationsbibliothek (TIB) · other · 2019

Abstract

When your SQL query reaches the DBMS, it's the optimizer job to decide how to execute it for you to get the result as fast as possible. To make this decision optimizer can examine the actual table data, but with multi giga- and terabyte tables, the only practical solution is to use various data statistics that was collected in advance. The better the statistics is and the more precisely it describes the actual data, the faster the plan will be, because optimizer image of the reality will be closer to the actual reality.

In this talk you'll learn what data statistics MariaDB and MySQL can collect, what statements do that, how to tell the optimizer to use it (it won't necessarily do it automatically!) and how it can make your queries many times faster. And, of course, when not to use indexes, when up-to-date statistics is enough.

Open the resolved locator · 10.5446/44404

Metadata licence: OpenAlex metadata (CC0)

Registry
OpenAlex DOI index + API
Fetched
2026-11-20 15:28 UTC
Cache state
not cached yet (bulk-index+openalex)
Locator
https://av.tib.eu/media/44404
Metadata licence
OpenAlex metadata (CC0)
Scope
Metadata as returned by the resolver; abstracts are never generated here.