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

ERROR HY000: Got error 190 "Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine....

    XMLWordPrintable

Details

    Description

      Problem (Slave SQL thread catches ERROR HY000: Got error 190 ...) found during RQG testing invoking DDL and row based binlogging.
      But the ugly things happen already without replication.

      CREATE TABLE t0 ( col1 INT, col2 INT ) ENGINE = MyISAM ;
      ALTER TABLE t0 ADD UNIQUE INDEX `uidx2` ( col1, col2 );
      ALTER TABLE t0 ADD UNIQUE INDEX `uidX1` ( col2 );
      ALTER TABLE t0 ADD PRIMARY KEY ( col2 );
      ALTER TABLE t0 CHANGE COLUMN col2 col2 INT;
      ERROR HY000: Got error 190 "Incompatible key or row definition between the MariaDB .frm file and the information in the storage engine. You have to dump an" from storage engine MyISAM
      The problem disappears in case the storage engine Aria or MEMORY is used.
      Replay on
      - 10.4 commit 5b4d6595d26aaaf0bf8bb3c9171cf1da96306a7c 2019-02-21
      - 10.3 commit 09bd2138522787a4e0b015695c462903f4a9e728 2019-02-22
       
      No replay with 10.2.22-MariaDB-debug
      10.2 commit af6fdc13072cc310cf17fd3b28c749515d9c563c 2019-02-19
       
      Workaround:
      Run a
           ALTER TABLE t0 DROP KEY `uidX1`;
      before the
          ALTER TABLE t0 ADD PRIMARY KEY ( col2 );
      
      

      Attachments

        1. prt
          1 kB
        2. t_s_5.test
          0.6 kB

        Issue Links

          Activity

            People

              midenok Aleksey Midenkov
              mleich Matthias Leich
              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.