[#MDEV-516] INSERT ON DUPLICATE KEY UPDATE + innodb_autoinc_lock

[MDEV-516] INSERT ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 broken, fixed in percona Created: 2012-09-07 Updated: 2012-09-19 Due: 2012-09-21 Resolved: 2012-09-19
Status:	Closed
Project:	MariaDB Server
Component/s:	None
Affects Version/s:	5.5.27, 5.3.8, 5.2.12, 5.1.62
Fix Version/s:	5.5.28, 5.3.9

Type:

Bug

Priority:

Major

Reporter:

Patryk Pomykalski

Assignee:

Michael Widenius

Resolution:

Fixed

Votes:

Labels:

None

Description

From percona: https://bugs.launchpad.net/percona-server/+bug/1035225

Concurrent INSERT ... ON DUPLICATE KEY UPDATE statements on a table with
an AUTO_INCREMENT column may result in spurious duplicate key errors
(and, as a result, lost data due to some rows being updated rather than
inserted) with the default value of innodb_autoinc_lock_mode=1.

Tested on 5.5.27 but 5.3.8 is most probably affected too.

Comments

Comment by Michael Widenius [ 2012-09-19 ]

Pushed into 5.5 tree

Generated at Thu Feb 08 06:29:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.

[MDEV-516] INSERT ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 broken, fixed in percona Created: 2012-09-07 Updated: 2012-09-19 Due: 2012-09-21 Resolved: 2012-09-19