A follow up to my blog post exploring how often we pick the optimal query plan. Instructions how to reproduce it, why it happens and how to address it.| Tomas Vondra
An evaluation of how often Postgres picks the optimal plan for simple scan queries.| Tomas Vondra
I keep saying this – we have the best and most skilled customers. Christian Klose from my Franconian home region contacted me via LinkedIn and asked for some assistance with an SR. I confess, I replied way too late (information overflow). But the finding Christian had is great to know. There are new interesting underscores for more than 255 _FIX_CONTROLs. Photo by Casey Horner on Unsplash Why don’t you see them in ORAdiff? As usual, I went to ORAdiff and tried to find out anything about t...| Upgrade your Database – NOW!
patch idea: dynamic tuning for IN queries| Tomas Vondra
Sometimes, the MySQL Optimizer chooses a wrong plan, and a query that should execute in less than 0.1 second ends-up running for 12 minutes ! This is not a new problem: bugs about this can be traced back to 2014, and a blog post on the subject dates of 2015. But even if this is old news, because this problem recently came to my attention, it is a problem worth writing on. This| J-F Gagné's MySQL Blog
Generally in MySQL we send queries massaged to a point where optimizer doesn’t have to think about anything. In our major user database environment 99.9% of queries don’t have alternati…| domas mituzas