pt-archiver doesn't honor b=1 flag to create SQL_LOG_BIN statement
Bug #903387 reported by
maxim.volkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Invalid
|
Undecided
|
Daniel Nichter | ||
2.0 |
Invalid
|
Undecided
|
Daniel Nichter | ||
2.1 |
Invalid
|
Undecided
|
Daniel Nichter |
Bug Description
Version: percona-
Full command:
pt-archiver \
--source h=localhost,
--dest h=localhost,
--columns column1,
--where "changed_when < '2011-12-01 00:00:00'" --limit 1000 --commit-each \
--nocheck-columns --replace --commit-each --bulk-insert --bulk-delete \
--statistics \
--no-check-charset \
--file '/tmp/mysql/
Issue: No ",b=1" nor ",b=true" flags won't create expected SET SQL_LOG_BIN = 0; statement neither with --dry-run nor with actual run.
Related branches
lp:~percona-toolkit-dev/percona-toolkit/test-pt-archiver-sql-log-bug-903387
- Daniel Nichter: Approve
-
Diff: 113 lines (+66/-17)1 file modifiedt/pt-archiver/basics.t (+66/-17)
lp:~percona-toolkit-dev/percona-toolkit/test-pt-archiver-sql-log-bug-903387-2.0
- Daniel Nichter: Approve
-
Diff: 97 lines (+59/-6)1 file modifiedt/pt-archiver/basics.t (+59/-6)
tags: | added: log-bin pt-archiver |
tags: | added: risk |
Changed in percona-toolkit: | |
status: | New → Triaged |
Changed in percona-toolkit: | |
milestone: | none → 2.1.3 |
Changed in percona-toolkit: | |
importance: | Undecided → High |
Changed in percona-toolkit: | |
status: | Triaged → In Progress |
assignee: | nobody → Daniel Nichter (daniel-nichter) |
To post a comment you must log in.
I cannot reproduce this. With 1.0 and 2.1 I see SET SQL_LOG_BIN=0 in the general log when running "pt-archiver --source F=/tmp/ 12345/my. sandbox. cnf,D=sakila, t=c,b=1 --purge --where 1=1 --no-check- charset" .
How are you verifying that SET SQL_LOG_BIN=0 is _not_ being set, Maxim?