marko acf84dfb75 branches/zip: Fast index creation: Lock the data dictionary only after ... acquiring the table lock. The data dictionary should not be locked for long periods. Before this change, in the worst case, the dictionary would be locked until the expiration of innodb_lock_wait_timeout. Virtually, transaction-level locks (locks on database objects, such as records and tables) have a latching order level of SYNC_USER_TRX_LOCK, which is above any InnoDB rw-locks or mutexes. However, the latching order of SYNC_USER_TRX_LOCK is never checked, not even by UNIV_SYNC_DEBUG. ha_innobase::add_index(), ha_innobase::final_drop_index(): Invoke row_mysql_lock_data_dictionary(trx) only after row_merge_lock_table().		2007-12-19 14:26:01 +00:00
..
ha_innodb.cc	branches/zip: innobase_mysql_end_print_arbitrary_thd(): Note that	2007-12-17 14:06:59 +00:00
ha_innodb.h	branches/zip: Merge 2116:2146 from trunk.	2007-11-30 12:30:21 +00:00
handler0alter.cc	branches/zip: Fast index creation: Lock the data dictionary only after	2007-12-19 14:26:01 +00:00
i_s.cc	branches/zip:	2007-12-18 09:44:03 +00:00
i_s.h	branches/zip: Move the implementation of the INFORMATION_SCHEMA tables	2007-10-03 14:00:54 +00:00
mysql_addons.cc	branches/zip:	2007-11-07 14:14:33 +00:00