Jon Olav Hauglid 9b30e2e29c Bug#11815600 [ERROR] INNODB COULD NOT FIND INDEX PRIMARY ... KEY NO 0 FOR TABLE IN ERROR LOG With the changes made by the patches for Bug#11751388 and Bug#11784056, concurrent reads are allowed while secondary indexes are created in InnoDB. This means that the metadata lock on the affected table is not upgraded to exclusive until the .FRM is updated at the end of ALTER TABLE processing. The problem was that if this lock upgrade failed for some reason (e.g. timeout), the index information in the server and inside InnoDB would be out of sync. This would happen since the add index operation already was committed inside InnoDB but the table metadata inside the server had not been updated yet. This patch fixes the problem by (for now) reverting the effects of the patches for Bug#11751388 and Bug#11784056. Concurrent reads will now again be blocked during creation of secondary indexes in InnoDB. Test case added to innodb_mysql_lock.test.		2011-03-09 16:06:13 +01:00
..
ha_innodb.cc	Bug#11815600 [ERROR] INNODB COULD NOT FIND INDEX PRIMARY	2011-03-09 16:06:13 +01:00
ha_innodb.h	Bug #57730 Clean up references to InnoDB Plugin	2010-10-27 09:54:20 +03:00
handler0alter.cc	Merge from mysql-5.1-innodb to mysql-5.5-innodb	2010-11-10 21:51:00 -08:00
i_s.cc	merge	2011-01-10 15:09:57 +02:00
i_s.h	Temporarily backout the Information Schema System Table Information Schema	2010-09-16 19:24:32 -07:00