• Monty's avatar
    MDEV-24532 Table corruption ER_NO_SUCH_TABLE_IN_ENGINE .. on table with foreign key · 676987c4
    Monty authored
    When doing a truncate on an Innodb under lock tables, InnoDB would rename
    the old table to #sql-... and recreate a new 't1' table. The table lock
    would still be on the #sql-table.
    
    When doing ALTER TABLE, Innodb would do the changes on the #sql table
    (which would disappear on close).
    When the SQL layer, as part of inline alter table, would close the
    original t1 table (#sql in InnoDB) and then reopen the t1 table, Innodb
    would notice that this does not match it's own (old) t1 table and
    generate an error.
    
    Fixed by adding code in truncate table that if we are under lock tables
    and truncating an InnoDB table, we would close, reopen and lock the
    table after truncate. This will remove the #sql table and ensure that
    lock tables is using the new empty table.
    
    Reviewer: Marko Mäkelä
    676987c4
truncate_foreign.result 2.3 KB