pt-heartbeat docs don't account for --utc

Reported by Roman Vynar on 2013-03-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Status tracked in 2.2
2.1
Low
Daniel Nichter
2.2
Low
Daniel Nichter

Bug Description

The doc is confusing, please see http://www.percona.com/doc/percona-toolkit/2.1/pt-heartbeat.html#cmdoption-pt-heartbeat--create-table
it says "UTC_TIMESTAMP()":
 INSERT INTO heartbeat (ts, server_id) VALUES (UTC_TIMESTAMP(), N);
...
 INSERT INTO heartbeat (id, ts) VALUES (1, UTC_TIMESTAMP());

But actually it does:
    729 Query INSERT INTO `percona`.`heartbeat` (server_id, ts) VALUES ('0', NOW())
or
    731 Query INSERT INTO `percona`.`heartbeat` (server_id, ts) VALUES ('0', UTC_TIMESTAMP())

depending --utc is used or not.

Please correct the doc as UTC is not always inserted.

Changed in percona-toolkit:
milestone: none → 2.2.1
importance: Undecided → Low
status: New → Triaged
tags: added: docs pt-heartbeat
Changed in percona-toolkit:
assignee: nobody → Daniel Nichter (daniel-nichter)
Daniel Nichter (daniel-nichter) wrote :

Actually, I'm going to retarget this to 2.1.10 because pt-heartbeat in 2.2 should alway use UTC, but that's another issue.

Changed in percona-toolkit:
milestone: 2.2.1 → 2.1.10
summary: - minor doc update pt-heartbeat 2.1.9
+ pt-heartbeat 2.1 docs don't account for --utc
Changed in percona-toolkit:
assignee: Daniel Nichter (daniel-nichter) → nobody
Changed in percona-toolkit:
assignee: nobody → Daniel Nichter (daniel-nichter)
summary: - pt-heartbeat 2.1 docs don't account for --utc
+ pt-heartbeat docs don't account for --utc
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers