Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
5.1.39 with InnoDB/XtraDB
Master/Slave configuration with following table on master:
CREATE TABLE `MailerType` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`active` tinyint(1) unsigned DEFAULT NULL,
`en_US` varchar(300) DEFAULT NULL,
`email_id` int(10) unsigned NOT NULL,
`min_resend_hours` int(10) unsigned DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
On slave the table is converted to InnoDB:
ALTER TABLE MailerType ENGINE=InnoDB;
Run following on master:
SET autocommit=0;
insert into MailerType (active, en_US, email_id, min_resend_hours, id)
values (1, 'OA bombs19', 13, null, 1501580);
commit;
rollback;
SET autocommit=1;
Result on master:
mysql> select * from MailerType;
-------------------------------------------------
| id | active | en_US | email_id | min_resend_hours |
-------------------------------------------------
| 1501580 | 1 | OA bombs19 | 13 | NULL |
-------------------------------------------------
1 row in set (0.00 sec)
Result on slave:
select * from MailerType;
Empty set (0.00 sec)
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: 5.1 transaction replication problem with InnoDBXtraDB
All development of XtraDB has moved under the Percona Server project - https://launchpad.net/percona-server - If this bug can be reproduced against current Percona Server, please file this bug against percona-server (you can simply do so by using the "Also affects project" link above).
Thanks,
Stewart Smith
Director of Server Development
Percona.
Re: 5.1 transaction replication problem with InnoDBXtraDB
No longer repeatable in MariaDB 5.5.
(There were a bunch of fixes related to mixed myisam/inno replication in 5.5)
Launchpad bug id: 493863
Re: 5.1 transaction replication problem with InnoDBXtraDB
In 5.0.87 this works fine.