• Marko Mäkelä's avatar
    MDEV-24818 Concurrent use of InnoDB table is impossible until the first transaction is finished · 92b2a911
    Marko Mäkelä authored
    In MDEV-515, we enabled an optimization where an insert into an
    empty table will use table-level locking and undo logging.
    This may break applications that expect row-level locking.
    
    The SQL statements created by the mysqldump utility will include the
    following:
    
        SET unique_checks=0, foreign_key_checks=0;
    
    We will use these flags to enable the table-level locked and logged
    insert. Unless the parameters are set, INSERT will be executed in
    the old way, with row-level undo logging and implicit record locks.
    92b2a911
innodb_trx_weight.test 3.6 KB