[MDEV-29481] mariadb-upgrade prints confusing statement Created: 2022-09-07 Updated: 2023-05-18 Resolved: 2022-10-22 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Storage Engine - InnoDB, Upgrades |
| Affects Version/s: | 10.4.26, 10.5.17, 10.6.9, 10.7.5, 10.8.4, 10.9.2, 10.10.1 |
| Fix Version/s: | 10.4.27, 10.5.18, 10.6.11, 10.7.7, 10.8.6, 10.9.4, 10.10.2, 10.11.1 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Oli Sennhauser | Assignee: | Alexander Barkov |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | regression-10.4 | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Description |
|
When running mariadb-upgrade it provides confusing statements: schema1.table1 At the end of the upgrade mariadb-upgrade does the ALTER TABLE FORCE itself. So user does not need to do it. 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... |
| Comments |
| Comment by Marko Mäkelä [ 2022-09-07 ] |
|
Thank you for the report. I think that we simply need a better fix of Demanding a table rebuild when only some metadata (.frm file contents) is in an old format feels excessive to me. |
| Comment by Alexander Barkov [ 2022-10-03 ] |
|
Hello serg. Can you please review patches in this branch: https://github.com/mariadb/server/tree/bb-10.4-bar-MDEV-29481
Thanks. |
| Comment by Alexander Barkov [ 2022-10-21 ] |
|
Hello serg. Can you please review a new version of patches in this branch: https://github.com/MariaDB/server/commits/bb-10.4-bar-MDEV-29481
|