PXC INSERT triggers on MyISAM tables insert additional rows on InnoDB tables
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL patches by Codership |
New
|
Undecided
|
Unassigned | ||
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Won't Fix
|
Undecided
|
Unassigned | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
This is probably related to bug 1064057, but it's also different:
CREATE TABLE `old` (
`id` int(11) NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`id`)
) ENGINE=MyISAM
CREATE TABLE `new` (
`id` int(11) NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`id`)
) ENGINE=InnoDB
character_
collation_
Database Collation: latin1_swedish_ci
INSERT INTO old VALUES (NULL); -- on the node where those ^ are created, yields:
+----+
| id |
+----+
| 1 |
+----+
1 row in set (0.00 sec)
+----+
| id |
+----+
| 1 |
+----+
1 row in set (0.00 sec)
But on another node:
+----+
| id |
+----+
| 2 |
+----+
1 row in set (0.01 sec)
+----+
| id |
+----+
| 1 |
| 2 |
+----+
2 rows in set (0.00 sec)
So table `new` on other nodes inserts an additional row. (The additional row also has the wrong auto-inc value due to bug 1080913).
Changed in percona-toolkit: | |
status: | New → Triaged |
Changed in codership-mysql: | |
status: | New → Confirmed |
Changed in percona-xtradb-cluster: | |
status: | New → Confirmed |
Changed in codership-mysql: | |
status: | Confirmed → New |
Changed in percona-toolkit: | |
milestone: | none → 2.2.1 |
importance: | Undecided → High |
Changed in percona-toolkit: | |
milestone: | 2.2.1 → none |
summary: |
- INSERT triggers on MyISAM tables insert additional rows on InnoDB tables + PXC INSERT triggers on MyISAM tables insert additional rows on InnoDB + tables |
Changed in percona-toolkit: | |
importance: | High → Undecided |
We've had about 8 months of experience with PXC now, and the verdict seems clear: PXC and MyISAM are not a good combination, and afaik there's no big push from users to make it work, i.e. the 99% use-case is PXC with InnoDB. So I'm going to WontFix this bug in Percona Toolkit.