pt-table-sync fails for point primary keys

Bug #1150452 reported by Daniël van Eeden
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

pt-table-sync doesn't seem to support a point primary key.

CREATE TABLE `geotest` (
  `g` geometry DEFAULT NULL,
  `p` point NOT NULL DEFAULT '',
  PRIMARY KEY (`p`(25))
) ENGINE=InnoDB DEFAULT CHARSET=latin1

$ pt-table-sync --replicate percona.checksums --print P=22384,u=root,p=msandbox,h=127.0.0.1
Argument "\0\0\0\0^A^A\0\0\0\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@" isn't numeric in numeric comparison (<=>) at /usr/bin/pt-table-sync line 2345. while doing test.geotest on 127.0.0.1

pt-table-sync 2.1.2

Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Not surprising: we've only ever tested standard BTREE indexes.

tags: added: chunking non-btree-index pt-table-sync
Changed in percona-toolkit:
status: New → Triaged
tags: added: spatial
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-1087

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.