This option suppresses all CREATE LOGFILE GROUP and CREATE TABLESPACE statements in the output of mysqldump. Certain options might require other privileges as noted in the option descriptions. Mysqldump requires at least the SELECT privilege for dumped tables, SHOW VIEW for dumped views, TRIGGER for dumped triggers, LOCK TABLES if the -single-transaction option is not used, and ( as of MySQL 5.7.31) PROCESS if the -no-tablespaces option is not used. So mysqldump now needs to be started by a user with enough privileges or using the -no-tablespaces option. mysqldump however tries to access the INFORMATION_SCHEMA.FILES table, which - as said above - now requires the PROCESS privilege. The said privilege PROCESS is not needed for most use cases. Imho a more practical solution for this breaking change would be to removed tablespaces in mysqldump by default and add a -add-tablespaces option instead.
Tableplus run stored function mysql how to#
It's a pity that this issue and how to solve it is not communicated better. So this issue has to happen on all machines having MySQL >= 5.7 and getting system updates eventually.īreaking Changes in minor updates are unexpected. Oracles bug tracker seems to be down however. The said issue number should be available here. Users who do not need to dump tablespace information can work around this requirement by invoking mysqldump with the -no-tablespaces option. This change affects users of the mysqldump command, which accesses tablespace information in the FILES table, and thus now requires the PROCESS privilege as well. Incompatible Change: Access to the INFORMATION_SCHEMA.FILES table now requires the PROCESS privilege. See 5.7.31 Release Notes / 8.0.21 Release Notes
Turns out this is a breaking change introduced in MySQL minor updates 5.7.31 and 8.0.21 in 2020/07. Not all at once, not on all commands, not on all users.
I experienced the same issue on some of my machines. Tl dr Breaking change introduced in minor MySQL update, use -no-tablespaces option in mysqldump from now on (recommended) or add the global PROCESS privilege to the user running the command.
0 kommentar(er)
