LP #1732625: mysqldump produces incorrect dumps with self-referenced foreign keys

**Reported in Launchpad by Paulus last update 11-12-2017 14:42:24

The percona build introduces --innodb-optimize-keys into the mysqldump utility. However it incorrectly works with foreign keys on the same table. For example this snippet produces an error on restore:

mysql -e 'create table test (a int, b int, index(a), index(b), foreign key (a) references test(b));' test
mysqldump test test > test.sql
mysql test < test.sql

The expected behaviour is to restore the table and not stop on the create table statement.