pt-table-sync fails for point primary keys
Bug #1150452 reported by
Daniël van Eeden
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,
Argument "\0\0\0\
pt-table-sync 2.1.2
tags: | added: spatial |
To post a comment you must log in.
Not surprising: we've only ever tested standard BTREE indexes.