Comment 5 for bug 1010232

Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

Now I'm trying out pt-table-checksum instead of pt-online-schema-change, and I find these two problems:

$ bin/pt-table-checksum --tables sakila.film_actor h=127.1,P=3306,D=sakila,t=film_actor,u=root --lock-wait-timeout=50 --chunk-index PRIMARY:3 --chunk-size 200
06-10T22:43:39 Cannot checksum table sakila.film_actor: Use of uninitialized value in exists at bin/pt-table-checksum line 2305.

[baron@localhost stabilize-test-suite]$ bin/pt-table-checksum --tables sakila.film_actor h=127.1,P=3306,D=sakila,t=film_actor,u=root --lock-wait-timeout=50 --chunk-index PRIMARY:1 --chunk-size 200
06-10T22:43:54 Skipping chunk 1 of sakila.film_actor because MySQL used only 2 bytes of the PRIMARY index instead of 4. See the --[no]check-plan documentation for more information.
            TS ERRORS DIFFS ROWS CHUNKS SKIPPED TIME TABLE
06-10T22:43:54 0 0 0 31 31 0.143 sakila.film_actor

The second problem is a bit subtle. I think it's because we might be using the entire index for the first-lower-boundary query?