Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.0.21, 10.1.22
-
None
-
Debian 8 (Jessie) and OpenSuSE 13.2
Description
We had in a MariaDB Training Standard Linux distros with standard MariaDB Installations and wanted to upgrade to the newest MariaDB 10.1 from MariaDB repository.
We later found out because of an error in journalcontrol that an upgrade from the DD never happened:
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)
|
we have the opinion that during upgrade MariaDB package should:
a) either upgrade with mysql_upgrade directly or
b) alternatively clearly should state that an upgrade is needed!
Regards,
Oli
Attachments
Issue Links
- duplicates
-
MDEV-19233 mysql_upgrade is not executed on package upgrade on Debian
- Closed
- is duplicated by
-
MDEV-24172 data structure tests for innodb_table_stats and innodb_index_stats incorrect
- Closed
- relates to
-
MDEV-12275 debian-start spams the syslog after an upgrade
- Closed