Task #13362

Move analyze table calls to the end of the upgrade process for 2.6

Added by José Raddaoui Marín almost 2 years ago. Updated almost 2 years ago.

Status:VerifiedStart date:06/17/2020
Priority:MediumDue date:
Assignee:-% Done:


Category:Migration task
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:2.6
Sponsored:No Requires documentation:


The upgrade task for the 2.6 release will perform many operations, including the upgrade to MySQL 8, the new charset and several modifications made over foreign keys and indexes. Running analyze table has a few benefits after all this changes:

- Performs and stores a key distribution analysis (if the table has not changed since the last one, its not analyzed again).
- Determines index cardinality, used for join optimizations.
- Removes the table from the definition cache.

This statements are already executed in the migration process in arMigration0178. However, we have added more changes and new tables after this migration and it would be better to move them to the end. Optionally, their are save enough to be run in all version upgrades, so we could move it outside the numbered migrations to execute it at the end of all future upgrades.


#1 Updated by José Raddaoui Marín almost 2 years ago

  • Status changed from New to QA/Review
  • Assignee deleted (José Raddaoui Marín)

Merged in qa/2.6.x. For testing, it only affects the upgrade-sql task and it was included before as part of the MySQL 8 upgrade changes, it's just executed at the end of all migrations now (and in future upgrades).

#2 Updated by Dan Gillean almost 2 years ago

I've just successfully run an upgrade. I'll keep this open a bit longer as I test related issues, but so far so good.

#3 Updated by Dan Gillean almost 2 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF