Extended mysqldump

Ignoring missing tables in mysqldump

In case table name was changed during the mysqldump process taking place, mysqldump would stop with error:

Couldn't execute 'show create table testtable'
Table 'testdb.tabletest' doesn't exist (1146)\n")

This could happen if mysqldump was taking a backup of a working slave and during that process table name would get changed. This error happens because mysqldump takes the list of the tables at the beginning of the dump process but the SHOW CREATE TABLE happens just before the table is being dumped.

With this option mysqldump will still show error to stderr, but it will continue to work and dump the rest of the tables.

Backup Locks support

In Percona Server 5.6.16-64.0 mysqldump has been extended with a new option, lock-for-backup (disabled by default). When used together with the --single-transaction option, the option makes mysqldump issue LOCK TABLES FOR BACKUP before starting the dump operation to prevent unsafe statements that would normally result in an inconsistent backup.

More information can be found on the Backup Locks feature documentation.

Compressed Columns support

In Percona Server 5.6.33-79.0 mysqldump has been extended to support Compressed columns with dictionaries feature. More information about the new options can be found on the Compressed columns with dictionaries feature page.

Taking backup by descending primary key order

In 5.6.35-81.0 new --order-by-primary-desc has been implemented. This feature tells mysqldump to take the backup by descending primary key order (PRIMARY KEY DESC) which can be useful if storage engine is using reverse order column for a primary key.

Version Specific Information