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

Can't write; duplicate key in table 'mysql.innodb_table_stats'

Details

    Description

      Run the following statements, in which the ALTER statement is expected to execute successfully. However, the ALTER statement failed, and it seems that the table `mysql.innodb_table_stats` does not timely update its info.

      CREATE TABLE t1 (c1 INT) ENGINE=InnoDB;
      		 
      CREATE TABLE t2 (c1 INT) ENGINE=InnoDB;
      		 
      ALTER TABLE t1 STATS_PERSISTENT 0;
      		 
      DROP TABLE IF EXISTS t1;
      		 
      ALTER TABLE t2 RENAME t1; -- [23000][1022] (conn=33) Can't write; duplicate key in table 'mysql.innodb_table_stats'

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          John Jove John Jove added a comment -

          By the way, If I create the same table t1 as follows, the execution results become valid.

          CREATE TABLE t1 (c1 INT) ENGINE=InnoDB STATS_PERSISTENT=0;
          		 
          CREATE TABLE t2 (c1 INT) ENGINE=InnoDB;
          		 
          DROP TABLE IF EXISTS t1;
          		 
          ALTER TABLE t2 RENAME t1; -- Normal

          John Jove John Jove added a comment - By the way, If I create the same table t1 as follows, the execution results become valid. CREATE TABLE t1 (c1 INT ) ENGINE=InnoDB STATS_PERSISTENT=0; CREATE TABLE t2 (c1 INT ) ENGINE=InnoDB; DROP TABLE IF EXISTS t1; ALTER TABLE t2 RENAME t1; -- Normal
          marko Marko Mäkelä added a comment -

          Thank you for the simple test case. I can reproduce this:

          10.6 2d5cba22a98e54c0c8975d8d7fe7e04981d73c8a

          		 
          mysqltest: At line 6: query 'ALTER TABLE t2 RENAME t1' failed: ER_DUP_KEY (1022): Can't write; duplicate key in table 'mysql.innodb_table_stats'

          The line number is off by one, because I added --source include/have_innodb.inc to make the input valid for our regression test tool.

          I think that the problem is that ALTER TABLE t1 STATS_PERSISTENT 0 fails to delete the statistics.

          marko Marko Mäkelä added a comment - Thank you for the simple test case. I can reproduce this: 10.6 2d5cba22a98e54c0c8975d8d7fe7e04981d73c8a mysqltest: At line 6: query 'ALTER TABLE t2 RENAME t1' failed: ER_DUP_KEY (1022): Can't write; duplicate key in table 'mysql.innodb_table_stats' The line number is off by one, because I added --source include/have_innodb.inc to make the input valid for our regression test tool. I think that the problem is that ALTER TABLE t1 STATS_PERSISTENT 0 fails to delete the statistics.
          marko Marko Mäkelä added a comment -

          I ended up fixing this so that ALTER TABLE t1 STATS_PERSISTENT=0 will delete the statistics.

          In DROP TABLE I would not try to drop InnoDB persistent statistics if they had not been enabled for the table. The reason is that there could be locking conflicts with other DDL statements that would make the operation fail, and many applications might not be prepared to deal with a failing DROP TABLE operation.

          marko Marko Mäkelä added a comment - I ended up fixing this so that ALTER TABLE t1 STATS_PERSISTENT=0 will delete the statistics. In DROP TABLE I would not try to drop InnoDB persistent statistics if they had not been enabled for the table. The reason is that there could be locking conflicts with other DDL statements that would make the operation fail, and many applications might not be prepared to deal with a failing DROP TABLE operation.

          People

            marko Marko Mäkelä
            John Jove John Jove
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.