Change in MySQL affects the mysqldump command

If you use the mysqldump command, you need to know about this change that affects you.

Unfortunately, in a bugfix version of MySQL, they have chosen to introduce a change that affects backwards compatibility. If you are aware of using the mysqldump command yourself in any script or to take your own backups of databases, you need to read on.

The change means that access to the INFORMATION_SCHEMA.FILES table now requires the PROCESS permission. The mysqldump command requires just that when accessing tablespace information.

To get around this, you can use mysqldump with the --no-tablespaces option. In most cases, you don’t need tablespace information in your dump.

A common use for the mysqldump command is to create custom backups of databases, or to migrate databases.

Applies to all servers except…

This change affects all our hosting servers as well as managed servers (i.e. not you with a VPS/DIY Server).

This fall we will be upgrading to MariaDB (a variant of MySQL) on all servers (hosting & managed server). MariaDB is not affected by this issue. If your server is upgraded to MariaDB, you don’t need to worry about this either.

Upgrades are ongoing throughout the fall and you can find an up-to-date list on our status page.