The latest version of pt-archiver (2.1) did successfully produced expected result.
Initial verification was by running on a test table, on a master. The table on a master and slave initially was identical. The expected result was - data would be removed on a master and still present on a slave. The actual result - data was removed on both sources.
Running with "--dry-run" didn't produce SET SQL_LOG_BIN=0 either.
Daniel,
The latest version of pt-archiver (2.1) did successfully produced expected result.
Initial verification was by running on a test table, on a master. The table on a master and slave initially was identical. The expected result was - data would be removed on a master and still present on a slave. The actual result - data was removed on both sources.
Running with "--dry-run" didn't produce SET SQL_LOG_BIN=0 either.