innodb_fake_changes doesn't handle duplicate keys on REPLACE

Bug #898306 reported by Mark Callaghan on 2011-11-30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona Server
Laurynas Biveinis
Valentine Gostev
Laurynas Biveinis

Bug Description

in this is done for REPLACE:
1) try insert
2) if insert fails then do delete and goto #1

When innodb_fake_changes is enabled this gets into an infinite loop.

I attached a patch that applies clean to mysql 5.1.52 + facebook patch. It includes a test case. But I am not sure if Percona likes to modify handler.h.

Related branches

Mark Callaghan (mdcallag) wrote :
Changed in percona-server:
assignee: nobody → Valentine Gostev (longbow)
Valentine Gostev (longbow) wrote :

also REPLACE does not work even after innodb_fake_changes is disabled. Works without innodb_fake_changes enabled after forced restart (SIGKILL)

Changed in percona-server:
status: New → Confirmed
importance: Undecided → High
Alexey Kopytov (akopytov) wrote :

Why is not targeted to any 5.5 milestone? We have a fix, why not fix it in 5.1.61?

Alexey Kopytov (akopytov) wrote :

Er, I mean 5.5.20-24.1.

tags: added: contribution
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers