• Sergei Petrunia's avatar
    MDEV-24351: S3, same-backend replication: Dropping a table on master... · 6859e80d
    Sergei Petrunia authored
    ..causes error on slave.
    Cause: if the master doesn't have the frm file for the table,
    DROP TABLE code will call ha_delete_table_force() to drop the table
    in all available storage engines.
    The issue was that this code path didn't check for
    HTON_TABLE_MAY_NOT_EXIST_ON_SLAVE flag for the storage engine,
    and so did not add "... IF EXISTS" to the statement that's written
    to the binary log.  This can cause error on the slave when it tries to
    drop a table that's already gone.
    6859e80d
replication_mixed.result 9.63 KB