This does not explain how does the upstream server end up in a similar
situation, but it's possible that MySQL Cluster somehpw triggers the
fast index creation path for InnoDB temp tables too.
** Changed in: percona-server/5.1
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/999147
Title:
A crash that leaves behind an InnoDB temporary table with indexes
results in an unbootable server
To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/999147/+subscriptions
--
Mailing list: https://launchpad.net/~enterprise-support
Post to : [email protected]
Unsubscribe : https://launchpad.net/~enterprise-support
More help : https://help.launchpad.net/ListHelp
