[MDEV-8115] mysql_upgrade crashes the server with REPAIR VIEW Created: 2015-05-07  Updated: 2015-05-15  Resolved: 2015-05-08

Status: Closed
Project: MariaDB Server
Component/s: Admin statements, Views
Affects Version/s: 5.5.43, 10.0.18
Fix Version/s: 5.5.44, 10.0.19

Type: Bug Priority: Blocker
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Duplicate
duplicates MDEV-8108 MariaDB 5.5.43 segfaults on startup Closed
duplicates MDEV-8117 REPAIR VIEW crashes thread Closed
Relates
relates to MDEV-6916 Upgrade from MySQL to MariaDB breaks ... Closed

 Description    

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



 Comments   
Comment by Stephen Tenberg [ 2015-05-08 ]

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).

Comment by Michaël de groot [ 2015-05-08 ]

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.

Comment by azurit [ 2015-05-15 ]

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?

Comment by Sergei Golubchik [ 2015-05-15 ]

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

Comment by azurit [ 2015-05-15 ]

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?

Comment by Sergei Golubchik [ 2015-05-15 ]

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.

Generated at Thu Feb 08 07:24:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.