--purge and --no-delete are mutually exclusive, but still allowed to be specified together by pt-archiver

Bug #1452914 reported by Sveta Smirnova on 2015-05-07
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Low
Frank Cizmich

Bug Description

Options --purge and --no-delete are mutually exclusive, but still can be specified together.

How to repeat:

pt-archiver --purge --no-delete --quick --no-check-charset --statistics --buffer --bulk-delete --primary-key-only --source h=127.0.0.1,P=13001,u=root,D=test,t=user --where="user='root'" --limit 200 --progress 200 --commit-each --dest h=127.0.0.1,P=13001,u=root,D=test,t=user_copy
TIME ELAPSED COUNT
2015-05-07T23:38:24 0 0
^CExiting on SIGINT.
2015-05-07T23:40:00 96 9
Started at 2015-05-07T23:38:24, ended at 2015-05-07T23:40:08
Source: D=test,P=13001,h=127.0.0.1,t=user,u=root
Dest: D=test,P=13010,h=127.0.0.1,t=user_copy,u=root
SELECT 10
INSERT 9
DELETE 0
Action Count Time Pct
commit 20 0.7237 0.69
inserting 9 0.0072 0.01
select 1 0.0002 0.00
other 0 103.5736 99.30

Suggested fix: do not allow to specify mutually exclusive options together.

Sveta Smirnova (svetasmirnova) wrote :

Version 2.2.14

Changed in percona-toolkit:
status: New → Confirmed
Changed in percona-toolkit:
status: Confirmed → Fix Committed
milestone: none → 2.3.1
importance: Undecided → Low
assignee: nobody → Frank Cizmich (frank-cizmich)
Frank Cizmich (frank-cizmich) wrote :

Fixed: Will issue error "--purge and --no-delete are mutually exclusive"

Changed in percona-toolkit:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-825

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers