pt-table-checksum doesn't process float values on different MySQL versions

Bug #1130876 reported by Aleksandr Kuzminsky on 2013-02-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit

Bug Description

There is a float column in a table.

In version 5.0 it's represented as:
points_first: 1e+06

In 5.5 -
points_first: 1000000

Although the number is the same pt-table-checksums treats the values as different.

tags: added: float-precision pt-table-checksum
Changed in percona-toolkit:
status: New → Triaged
Brian Fraser (fraserbn) wrote :

Aleksandr, are you using --float-precision? If not, that's the solution for your problem. If yes and the problem is still there, could you attach the output of the tool while running with PTDEBUG=1?

Changed in percona-toolkit:
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Percona Toolkit because there has been no activity for 60 days.]

Changed in percona-toolkit:
status: Incomplete → Expired
joffrey92 (joffreymi) wrote :


the issue is for display, not really for precision.

Still in 2015, quite a lot of 5.0 (and older) are running production systems, and are finally being upgraded.

The patch proposed from :

Could be integrated, as an option maybe, to avoid false positives when comparing checksums between versions v5.0 and 5.5


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

Other bug subscribers