InnoDB requires a full table rebuild for foreign key changes. So it doesn't make sense to delay their creation by moving them from CREATE TABLE to a separate ALTER TABLE in a mysqldump output.
So --innodb-optimize-keys should ignore foreign key constrains. Documentation for innodb_expand_fast_index_creation.patch should be changed to reflact that.
InnoDB requires a full table rebuild for foreign key changes. So it doesn't make sense to delay their creation by moving them from CREATE TABLE to a separate ALTER TABLE in a mysqldump output.
So --innodb- optimize- keys should ignore foreign key constrains. Documentation for innodb_ expand_ fast_index_ creation. patch should be changed to reflact that.