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

mysql_upgrade crashes the server with REPAIR VIEW

Details

    Description

      create table t1 (a blob);
      create view v1 as select * from t1;
      repair view v1;

      Attachments

        Issue Links

          Activity

            This happened to me upon trying to upgrade to 10.0.18 on Ubuntu 14.04. I traced it to two views. (The rest of the views didn't trigger the crash). After dropping the two views I did a full mysql_upgrade --force and was able to start the server normally (and then add back the two simple views).

            stephentenberg Stephen Tenberg added a comment - This happened to me upon trying to upgrade to 10.0.18 on Ubuntu 14.04. I traced it to two views. (The rest of the views didn't trigger the crash). After dropping the two views I did a full mysql_upgrade --force and was able to start the server normally (and then add back the two simple views).

            I was able to work around this by dropping this view (MDEV-8117) and adding it again after running mysql_upgrade. There are over 100 views in the installation, fortunatelty only 1 caused issues.

            michaeldg Michaël de groot added a comment - I was able to work around this by dropping this view ( MDEV-8117 ) and adding it again after running mysql_upgrade. There are over 100 views in the installation, fortunatelty only 1 caused issues.
            azurit azurit added a comment - - edited

            We were experiencing this crash even when upgrading from 5.5.42 to 5.5.43 on SEVERAL servers (it crashed during REPAIR query). I just read the warning that we shouldn't upgrade but we already did and it was crashing most of the time - what damage was done to our data? How should we repair it?

            azurit azurit added a comment - - edited We were experiencing this crash even when upgrading from 5.5.42 to 5.5.43 on SEVERAL servers (it crashed during REPAIR query). I just read the warning that we shouldn't upgrade but we already did and it was crashing most of the time - what damage was done to our data? How should we repair it?

            No damage whatsoever. Just don't run mysql_upgrade when upgrading from 5.5.42 and you're fine.

            serg Sergei Golubchik added a comment - No damage whatsoever. Just don't run mysql_upgrade when upgrading from 5.5.42 and you're fine.
            azurit azurit added a comment -

            As i said, we already did and it did crash on several servers during the upgrade process (5.5.42 -> 5.5.43). Does the upgrade script needs to be run again or next MariaDB version (5.5.44) will fix it automatically?

            azurit azurit added a comment - As i said, we already did and it did crash on several servers during the upgrade process (5.5.42 -> 5.5.43). Does the upgrade script needs to be run again or next MariaDB version (5.5.44) will fix it automatically?

            Your tables and views are ok, there is nothing wrong with the data. The bug was in mysqld binary and when it'll be replaced with the next version the bug will go away.

            serg Sergei Golubchik added a comment - Your tables and views are ok, there is nothing wrong with the data. The bug was in mysqld binary and when it'll be replaced with the next version the bug will go away.

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.