
MariaDB and MySQL — what statistics optimizer needs (froscon2019)
or when and how not to use indexes
Chaos Computer Club - archive feed · Sergei Golubchik
August 10, 201926m 11s
Audio is streamed directly from the publisher (cdn.media.ccc.de) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
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.
When your SQL query reaches the DBMS, it's the optimizer's 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 gigabyte and terabyte tables, the only practical solution is to use various data statistics that were collected in advance. The better the statistics and the more precisely it describes the actual data, the faster the plan will be, because the optimizer image of 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.
about this event: https://programm.froscon.de/2019/events/2343.html
Topics
froscon20192343Databases