Bug #86457 DIFFERENT MYSQL SCEHMA AFTER UPGRADE
Submitted: 25 May 2017 13:45 Modified: 20 Jun 2017 17:15
Reporter: Abhishek Ranjan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Data Dictionary Severity:S3 (Non-critical)
Version:8.0.2 OS:Any
Assigned to: CPU Architecture:Any

[25 May 2017 13:45] Abhishek Ranjan
Description:
The contents of mysql schema is different for a 
upgraded database from 5.7 when compared to new created database in trunk.
The difference is behavior is due to WL#9532 while moves the creation of all
system tables to mysql tablespace. Same should be done for the existing system
tables.

How to repeat:
- Initialize a new data directory with 8.0.2 (latest trunk) code.
- Inspect the content of <data_directory>/mysql 
- Initialize a data directory in 5.7
- Start 8.0.2 server on it ( upgrade the data directory)
- Execute mysql_upgrade 
- Inspect the content of <data_directory>/mysql/

Suggested fix:
mysql_upgrade should move existing system tables to mysql tablespace.
[20 Jun 2017 17:15] Daniel Price
Posted by developer:
 
This bug was introduced and fixed in 8.0.2, which is not yet released. It should not be encountered by and end user. No changelog entry required.