Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-16909

RBR aborts with ER_NO_SUCH_TABLE upon RENAME on temporary table

    XMLWordPrintable

Details

    Description

      --source include/have_binlog_format_row.inc
      --source include/master-slave.inc
       
      CREATE TEMPORARY TABLE t1 (a INT);
      --error 0,1146
      RENAME TABLE t1 TO tmp;
       
      --sync_slave_with_master
      --connection master
      --source include/rpl_end.inc
      

      10.0 9dfef6e29b9

      180807  3:38:56 [ERROR] Slave SQL: Error 'Table 'test.t1' doesn't exist' on query. Default database: 'test'. Query: 'RENAME TABLE t1 TO tmp', Gtid 0-1-1, Internal MariaDB error code: 1146
      180807  3:38:56 [Warning] Slave: Table 'test.t1' doesn't exist Error_code: 1146
      180807  3:38:56 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000001' position 313
      180807  3:38:56 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 313
      

      The replication problem appeared in 10.0.27 release after the commit below made RENAME on temporary table possible.

      commit bf2e31500c9a0a7fcdccfb724e9447347a3ab684
      Author: Alexey Botchkov <holyfoot@askmonty.org>
      Date:   Mon Jul 18 11:50:08 2016 +0400
       
          MDEV-8569 build_table_filename() doesn't support temporary tables.
          
                  Temporary tables support added for RENAME and ALTER TABLE.
      

      Attachments

        Issue Links

          Activity

            People

              Elkin Andrei Elkin
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.