Re:Move Fast and Migrate Things: How We Automated Migrations...
by jclulow on Thursday February 07, 2019 @01:14AM
(#19103403)
One challenge with that is that the query plan often depends on the current table composition statistics. If a value is relatively common (or uncommon), or the size of the table has grown or shrunk, you may end up with a materially different (and conceivably substantially worse) plan.
Re:Move Fast and Migrate Things: How We Automated Migrations...
by tomnipotent on Thursday February 07, 2019 @01:23AM
(#19103426)
I can't tell you how many times over 20 years I've heard a DBA tell me "the statistics weren't updated" after an incident.
Re:Move Fast and Migrate Things: How We Automated Migrations...
by ovi256 on Thursday February 07, 2019 @07:46AM
(#19104862)
I've written cron jobs to update mysql statistics to prevent it from choosing bad query plans. It's as terrible as it sounds.
Re:Move Fast and Migrate Things: How We Automated Migrations...
by pas on Thursday February 07, 2019 @09:04AM
(#19105261)
How come it's not automatic and built-in? Why is a script terrible? (Does it have to enumerate all tables and piecewise run the stat update?)
Both Postgres & SQL Server support EXPLAIN on DML without running the statement (with varying levels of depth).