• Dmitry Lenev's avatar
    Fix for bug #11762012 - "54553: INNODB ASSERTS IN · 915d24d0
    Dmitry Lenev authored
    HA_INNOBASE::UPDATE_ROW, TEMPORARY TABLE, TABLE LOCK".
    
    Attempt to update an InnoDB temporary table under LOCK TABLES
    led to assertion failure in both debug and production builds
    if this temporary table was explicitly locked for READ. The
    same scenario works fine for MyISAM temporary tables.
    
    The assertion failure was caused by discrepancy between lock
    that was requested on the rows of temporary table at LOCK TABLES
    time and by update operation. Since SQL-layer requested a
    read-lock at LOCK TABLES time InnoDB engine assumed that upcoming
    statements which are going to be executed under LOCK TABLES will
    only read table and therefore should acquire only S-lock.
    An update operation broken this assumption by requesting X-lock.
    
    Possible approaches to fixing this problem are:
    
    1) Skip locking of temporary tables as locking doesn't make any
       sense for connection-local objects.
    2) Prohibit changing of temporary table locked by LOCK TABLES ...
       READ.
    
    Unfortunately both of these approaches have drawbacks which make
    them unviable for stable versions of server.
    
    So this patch takes another approach and changes code in such way
    that LOCK TABLES for a temporary table will always request write
    lock. In 5.5 version of this patch switch from read lock to write
    lock is done on SQL-layer.
    
    mysql-test/suite/innodb/r/innodb_mysql.result:
      Added test for bug #11762012 - "54553: INNODB ASSERTS IN
      HA_INNOBASE::UPDATE_ROW, TEMPORARY TABLE, TABLE LOCK".
    mysql-test/suite/innodb/t/innodb_mysql.test:
      Added test for bug #11762012 - "54553: INNODB ASSERTS IN
      HA_INNOBASE::UPDATE_ROW, TEMPORARY TABLE, TABLE LOCK".
    sql/sql_parse.cc:
      Since a temporary table locked by LOCK TABLES can be updated even
      if it was only locked for read we always request TL_WRITE locks
      for such tables at LOCK TABLES time. This allows to avoid 
      discrepancy between locks acquired at LOCK TABLES time and by
      a statement executed under LOCK TABLES. Such a discrepancy has
      caused problems for InnoDB storage engine.
      
      To support this change a part of code implementing LOCK TABLES 
      has been moved to a helper function.
    915d24d0
innodb_mysql.result 74.5 KB