pt-table-sync fails for point primary keys

Reported by Daniël van Eeden on 2013-03-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
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

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers