Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 10.0.5
-
Fix Version/s: 10.0.7
-
Component/s: None
-
Labels:None
-
Environment:MariaDB RPM packages installed via yum on Centos 6.4 on EC2
Description
Access to our partitioned tables broke after upgrading from 10.0.3-1 to 10.0.5-1.
example:
MariaDB [aggregation_new]> describe blarf\G
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'ALGORITHM = 2 */ (campaign_id)
PARTITIONS 8' at line 1
the "blarf" table is partitioned like: (from another server)
mysql> show create table udid \G
*************************** 1. row ***************************
Table: blarf
Create Table: CREATE TABLE `blarf` (
`blarf` char(40) NOT NULL,
`cuttle_id` int(10) unsigned NOT NULL COMMENT ' ',
`thing_time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`conversion_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`cuttle_id`,`blarf`),
KEY `thing_time_idx` (`thing_time`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
/*!50100 PARTITION BY KEY (cuttle_id)
PARTITIONS 8 */
1 row in set (0.00 sec)
We cannot select or update the "blarf" table or the other 2 partitioned tables. All 3 tables have the same partitioning scheme.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Note that I was able to restore the DB using a MySQLdump from another server, and it worked fine.
So it would appear to be some sort of innodb version-compatibility or migration issue.
It is a large DB that takes 1/2 day to restore so it would be difficult to reproduce. Also, I don't know where to get old versions of MariaDB in RPM format.