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

RBR does not work with CSV tables

    XMLWordPrintable

Details

    Description

      --source include/have_binlog_format_row.inc
      --source include/master-slave.inc
       
      CREATE TABLE t (a INT NOT NULL) ENGINE=CSV;
      INSERT INTO t VALUES (1),(2);
      DELETE FROM t;
       
      --sync_slave_with_master
       
      # Cleanup
      --connection master
      DROP TABLE t;
      --source include/rpl_end.inc
      

      10.5 855c21eb99a5c6a6f9eb52eea6ce7d3279a9f8c3

      2024-10-22 19:57:59 7 [ERROR] mariadbd: Can't find record in 't'
      2024-10-22 19:57:59 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table test.t; Can't find record in 't', Error_code: 1032; handler error HA_ERR_END_OF_FILE; the event's master log master-bin.000001, end_log_pos 898, Gtid 0-1-3, Internal MariaDB error code: 1032
      2024-10-22 19:57:59 7 [Warning] Slave: Can't find record in 't' Error_code: 1032
      2024-10-22 19:57:59 7 [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 733
      

      It goes all the way back to 5.x versions, reproducible both on MySQL and MariaDB 5.5, but not on MySQL 5.6. I can only guess that we never bothered to file it back at the beginning because it was an upstream issue, but by the time when it was eventually fixed in MySQL 5.6, the versions already diverged and we weren't merging all bugfixes anymore.

      Attachments

        Activity

          People

            knielsen Kristian Nielsen
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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