MySQL Bugs: #51854: Details of mysqlbinlog command output

Bug #51854	Details of mysqlbinlog command output
Submitted:	9 Mar 2010 6:11	Modified:	25 Mar 2010 19:49
Reporter:	Mikiya Okuno	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
The refman doesn't describe what do values on the header comment of mysqlbinlog command mean. Each log event is proceeded by a header comment like below:

# at 141
#100309  9:28:36 server id 123  end_log_pos 245 	Query	thread_id=3350	exec_time=11	error_code=0

In the first line
"at" means a binlog position where this event starts

In the second line
It start with a timestamp when a query started on a master. This value is kept on slaves' binary log, and be propagated to slave's slaves.
"server id" is server_id where this event is originally recorded.
"end_log_pos" indicates where this log event ends
"exec_time" is time taken to execute this event on a master. on slaves, it indicates (timestamp when a query started on a master) - (timestamp when a query finished on a slave). So, it can be a good indicator to determine how much the replication is lagging behind.
"error_code" is an error code reported on a master as a result of this query.

http://dev.mysql.com/doc/refman/5.1/en/mysqlbinlog.html

How to repeat:
n/a

Suggested fix:
please add some explanation on http://dev.mysql.com/doc/refman/5.1/en/mysqlbinlog.html etc

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.