table with no PK but still having UK, can cause crash in slave using PA

Bug #1003929 reported by Seppo Jaakola on 2012-05-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Seppo Jaakola
Seppo Jaakola

Bug Description

Confused? You won't be after reading this description:

If a table has no primary key (PK) assigned, but defines one or several unique keys (UK), then certain transactions on this table can cause problems with slaves which have parallel applying (PA) configured.

This issue surfaced with Drupal6 application using apache-solr module connected to a solr server.

A separate regression test has been implemented and it can reproduce this problem in just few secs.

Related branches

This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers