pt-online-schema-change logging
Bug #1182222 reported by
MarcODell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Request per Ryan H, Director of Percona Remote DBA Team:
Currently pt-osc has the following output:
Determining the method to update foreign keys...
`dhub_n16`.`Error`: too many rows: 13383718; must use drop_swap
Drop-swapping tables...
Dropped and swapped tables OK.
Dropping triggers...
Dropped triggers OK.
Successfully altered `dhub_n16`
When using drop swap there is some production impact. I would like that to be measured by outputting the current timestamp on the above lines so we know the duration of the impact.
Thank you,
Cheers!
Marc O'Dell
Percona Remote DBA Team
Revision history for this message
| Daniel Nichter (daniel-nichter) wrote | #1 |
| tags: | added: pt-online-schema-change |
| Changed in percona-toolkit: | |
| status: | New → Invalid |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Agreed, created https:/