Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.0.20-galera
-
None
-
Debian 7.8
MaxScale 1.2.1
wsrep_auto_increment_control=OFF
wsrep_sync_wait=1
auto_increment_increment=1
MaxScale configured with R/W Split
Description
Similar to, but not exactly the same as http://bugs.mysql.com/bug.php?id=65116.
Only shows up on cluster, standalone install work fine.
Create the following table:
CREATE TABLE `auto_inc` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`data` varchar(45) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `data_UNIQUE` (`data`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
Insert some data using REPLACE INTO:
REPLACE INTO auto_inc (data) VALUES ('Hello');
SHOW TABLE STATUS LIKE 'auto_inc' shows Auto_increment set to 2.
Issue the same query again:
REPLACE INTO auto_inc (data) VALUES ('Hello');
The row is now updated with id=2, but auto_increment is unchanged. On next insert this will result in duplicate key error.
Attachments
Issue Links
- relates to
-
MDEV-10379 Failing assertion: xid_seqno > trx_sys_cur_xid_seqno
- Closed