Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2, 10.10.1
Description
When running mariadb-upgrade it provides confusing statements:
schema1.table1
error : Table rebuild required. Please do "ALTER TABLE `table1` FORCE" or dump/reload to fix it!
schema1.table2 OK
schema1.table3
error : Table rebuild required. Please do "ALTER TABLE `table3` FORCE" or dump/reload to fix it!
schema1.table4 OK
...
`schema1`.`table1` FIXED
`schema1`.`table4` FIXED
At the end of the upgrade mariadb-upgrade does the ALTER TABLE FORCE itself. So user does not need to do it.
So it would be more meaningful to print a message like "Table rebuild required. I do it further down..."
Customer was confused (an I was as well when reading the first time).
Would be a good task for a simple community contribution if it will be decided to be implemented...
Attachments
Issue Links
- blocks
-
MDEV-28822 Table from older version requires table rebuild when adding column to table with multi-column index
- Closed
- is blocked by
-
MDEV-29672 Add MTR tests covering key and key segment flags and types
- Closed
- is caused by
-
MDEV-20704 An index on a double column erroneously uses prefix compression
- Closed
-
MDEV-28727 ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade
- Closed
- relates to
-
MDEV-28822 Table from older version requires table rebuild when adding column to table with multi-column index
- Closed
-
MDEV-29495 Generalize can_convert_xxx() hook engine API to cover any arbitrary data type
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...