~drizzle-trunk/drizzle/development

Viewing all changes in revision 1819.9.130.

  • Committer: Stewart Smith
  • Author(s): Marko Mäkelä
  • Date: 2010-12-06 04:04:11 UTC
  • mto: (2021.1.2 build)
  • mto: This revision was merged to the branch mainline in revision 1986.
  • Revision ID: stewart@flamingspork.com-20101206040411-sgd7ltb1cets6oh4
Merge Revision revid:marko.makela@oracle.com-20100819103637-objk0u6uvc6vj4m5 from MySQL InnoDB

Original revid:marko.makela@oracle.com-20100819103637-objk0u6uvc6vj4m5

Original Authors: Marko Mäkelä <marko.makela@oracle.com>
Original commit message:
Bug#56114 Disallow trx->dict_operation_lock_mode==RW_X_LATCH in srv_suspend_mysql_thread()

Issue an error message to the error log when
trx->dict_operation_lock_mode == RW_X_LATCH in
srv_suspend_mysql_thread(). Transactions that modify InnoDB
data dictionary tables must be free of lock waits, because they
must be holding the data dictionary latch in exclusive mode.
The transactions must not be accessing any other tables other than
the data dictionary tables.

The handling of RW_X_LATCH was accidentally added in the InnoDB Plugin,
as a wrong fix of an assertion failure. (Fast index creation was accessing
both data dictionary tables and user tables in the same transaction.)

expand all expand all

Show diffs side-by-side

added added

removed removed

Lines of Context: