pt-online-schema-change timestamp output

Registered by Daniel Nichter

From bug 1182222:

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`.`DataPoint`.

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.

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
Daniel Nichter
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2.2.4
Started by
Daniel Nichter
Completed by
Daniel Nichter

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.