Here are the workarounds we've had to implement to prevent these rocksdb patches from breaking our automation:
1. mysqldump 5.6.36 and 5.7.18 want to be able to query performance_schema, which is not available to non-root users by default.
Solution: INSERT INTO mysql.db SET host='%', user='', db='performance_schema',Select_priv='Y'
2. importing dumps from 5.6.36 into 5.7.18 breaks due to show_compatibility_56 being off by default in >5.7.6.
Solution: SET GLOBAL show_compatibility_56 = ON and set in my.cnf
These rocksdb patches seem very poorly thought out. Was no consideration given to dumps being run against servers with PFS disabled, imported by non-root users, or portability across versions?
Here are the workarounds we've had to implement to prevent these rocksdb patches from breaking our automation:
1. mysqldump 5.6.36 and 5.7.18 want to be able to query performance_schema, which is not available to non-root users by default.
Solution: INSERT INTO mysql.db SET host='%', user='', db='performance _schema' ,Select_ priv='Y'
2. importing dumps from 5.6.36 into 5.7.18 breaks due to show_compatibil ity_56 being off by default in >5.7.6.
Solution: SET GLOBAL show_compatibil ity_56 = ON and set in my.cnf
These rocksdb patches seem very poorly thought out. Was no consideration given to dumps being run against servers with PFS disabled, imported by non-root users, or portability across versions?