[MDEV-17988] mysql_upgrade failed to revert innodb_index/table_stats tables column datatype length Created: 2018-12-12  Updated: 2019-01-14  Resolved: 2019-01-14

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Muhammad Irfan Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback

Issue Links:
Relates
relates to MDEV-14637 Latching order violation during btr_c... Closed

 Description   

table_name field in both tables (innodb_table_stats & innodb_index_stats) are increased to 199 from 64 for VARCHAR in 10.2.17
However, downgrading it back to 10.2.15 didn't changed VARCHAR(199) to VARCHAR(64)

$ mysql_upgrade --upgrade-system-tables
 
 
 
The --upgrade-system-tables option was used, user tables won't be touched.
 
 
 
Phase 1/7: Checking and upgrading mysql database
 
Processing databases
 
 
 
mysql
 
.
 
mysql.innodb_index_stats OK
 
mysql.innodb_table_stats OK
 
.
 
Phase 7/7: Running 'FLUSH PRIVILEGES'
 
OK



 Comments   
Comment by Elena Stepanova [ 2018-12-12 ]

mysql_upgrade doesn't downgrade, it's an upgrade script, as the name suggests.

There is no formal downgrade procedure, and neither is it guaranteed to work between an arbitrary pair of releases – usually it would (between close enough minor releases), but sometimes it won't.

Comment by Marko Mäkelä [ 2018-12-13 ]

The table definition was corrected as part of the MDEV-14637 fix in MariaDB Server 10.2.17 and 10.3.9.

Generated at Thu Feb 08 08:40:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.