| Summary: | dev-db/mariadb-10.1.7_rc complains about type mismatch and falls back on using transient stats | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Attila Tóth <atoth> |
| Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://mariadb.atlassian.net/browse/MDEV-6349 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
You must run mysql_upgrade on every minor version change. 10.0 -> 10.1 requires it. This has always been true for dev-db/mysql as well. 5.5 -> 5.6 and soon 5.6 -> 5.7 |
2015-09-17 00:31:55 3c786628700 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch). 2015-09-17 00:31:55 3c786628700 InnoDB: Error: Fetch of persistent statistics requested for table "mysql"."gtid_slave_pos" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead. Reproducible: Always Solution: mysql> ALTER TABLE `mysql`.`innodb_table_stats` MODIFY `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP; mysql> ALTER TABLE `mysql`.`innodb_index_stats` MODIFY `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP; I haven't started mysql_upgrade, since it wasn't a major version bump.