Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Incomplete
-
10.2(EOL)
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
|
Attachments
Issue Links
- relates to
-
MDEV-14637 Latching order violation during btr_cur_pessimistic_delete()
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Labels | need_feedback |
Link |
This issue relates to |
Fix Version/s | N/A [ 14700 ] | |
Resolution | Incomplete [ 4 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 91210 ] | MariaDB v4 [ 155357 ] |
Zendesk Related Tickets | 160217 |
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.