Il 11 maggio 2019 00:27:28 CEST, joshua stein <j...@openbsd.org> ha scritto: >On Fri, 10 May 2019 at 16:39:49 -0400, Jeremie Courreges-Anglas wrote: >> >> This is a follow-up of this thread: >> >> https://marc.info/?l=openbsd-ports&m=155215322716829&w=2 >> >> Everything looks fine regarding the ports tree. I have successfully >> built all* consumers (BUILD/LIB_DEPENDS) on amd64 and I can't find >any >> local mariadb patch left in my tree**. bulk build still churning on >> sparc64. >> >> I also did some minimal testing of the server part, but I would >prefer >> reports from actual users. I have no idea what the migration path >looks >> like. > >I tested with a large database from 10.0.38 and the 10.2.23 server >started just fine, with no regressions in the application test suite >on the same machine (using Ruby with the mysql2 gem). > >I did get some warnings logged to the mysqld log: > >2019-05-10 18:19:16 9081375072320 [Warning] InnoDB: Table >mysql/innodb_table_stats has length mismatch in the column name >table_name. Please run mysql_upgrade >2019-05-10 18:19:16 9081375072320 [ERROR] InnoDB: Column last_update in >table `mysql`.`innodb_table_stats` is INT UNSIGNED NOT NULL but should >be BINARY(4) NOT NULL (type mismatch). >2019-05-10 18:19:16 9081375072320 [ERROR] InnoDB: Fetch of persistent >statistics requested for table `XXX`.`keystores` 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. > >But running 'mysql_upgrade' squelched them.
You should run mysql_upgrade after every major update, other than that it's best practice to update your slave mysql server before the master. Giovanni
