[MDEV-22683] mysql_upgrade misses some changes to mysql schema Created: 2020-05-23 Updated: 2023-03-03 Resolved: 2023-03-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients, Upgrades |
| Affects Version/s: | 10.1, 10.2, 10.3, 10.4, 10.5 |
| Fix Version/s: | 10.11.3, 11.0.2, 10.4.29, 10.5.20, 10.6.13, 10.8.8, 10.9.6, 10.10.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Daniel Black |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | beginner-friendly | ||
| Description |
|
Over the time and different versions, some structures in mysql schema get changed, but not all the changes make it to the scripts executed by mysql_upgrade. It means that a schema freshly created by mysql_install_db on a version 10.x.y differs from a schema created on an earlier version and upgraded to 10.x.y by mysql_upgrade. All diffs below are from diff -u <upgraded schema> <newly created schema>. 5.5 => 10.0+
10.1 => 10.2+
10.4 => 10.5
10.3 => 10.4+ This is not a miss, but a difference worth mentioning. With the same 10.4 build in the same environment, on a newly created schema I get mysql.user with charset latin1, while upon upgrade from 10.3 – with utf8.
|
| Comments |
| Comment by Elena Stepanova [ 2020-05-23 ] |
|
Assigned to serg for the unlikely possibility that [some of] the omissions are intentional. |
| Comment by Sergei Golubchik [ 2020-05-28 ] |
|
You're right, they are not intentional, as far as I can see |
| Comment by Daniel Black [ 2023-03-02 ] |
|
10.4 resolved thanks to Lorna Luo from AWS. Didn't resolve mysql.user view - hasn't caused a problem that I've seen. Can relook if needed. Anticipating 10.5 fix per PR #2511 |
| Comment by Daniel Black [ 2023-03-03 ] |
|
Forgotten my own work: MDEV-30065: mariadb-install-db --enforce-storage-engine=InnoDB fails … pr #2437 - changes help_relation to remove the FK and add the secondary index help_topic_id, which this MDEV required anyway. |