pt-online-schema-change can silently drop rows

Bug #1225577 reported by Rob Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Triaged
Undecided
Unassigned

Bug Description

When adding a unique index on a table with pt-online-schema-change, it silently drops rows that fail the unique constraint. There should be the option to check that the row counts are the same before swapping tables.

Yes, we should check to verify that the columns are unique before running, but there are times the tools insert non-unique rows while PTOSC is running, thus having a final check would be best.

tags: added: risk
Changed in percona-toolkit:
status: New → Triaged
Revision history for this message
Jericho Rivera (jericho-rivera) wrote :

This looks like this has been fixed in pt-osc 3.0.4 with --check-unique-index-change option.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1151

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.