MySQL Bugs: #69717: DML statements replicated via RBR are not logged in the general query log

Bug #69717	DML statements replicated via RBR are not logged in the general query log
Submitted:	10 Jul 2013 18:14	Modified:	16 Jul 2013 16:44
Reporter:	Valeriy Kravchuk	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1, 5.5, 5.6	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
As far as I understand from http://bugs.mysql.com/bug.php?id=14722, it is expected and even "by design" that slave writes nothing to General Query Log when executing RBR events. I wonder though why this is not mentioned at http://dev.mysql.com/doc/refman/5.6/en/query-log.html or at any other manual page (correct me if I am wrong).

How to repeat:
Start replication with binlog-format=ROW (or MIXED) on master, enable general query log on slave and then create some table and INSERT, then UPDATE some rows. Check general query log content on slave.

Suggested fix:
Document this properly and explicitly or implement http://bugs.mysql.com/bug.php?id=14722.

On 5.6 perhaps the general log should log the query event associated with the RBR if it is available?

Hello Valeriy,

Thank you for the report.

Some relevant info is documented in the manual page http://dev.mysql.com/doc/refman/5.6/en/replication-sbr-rbr.html

Under Disadvantages of row-based replication - "You cannot examine the logs to see what statements were executed, nor can you see on the slave what statements were received from the master and executed."

But yes, good to have some details in the page too - http://dev.mysql.com/doc/refman/5.6/en/query-log.html

Thanks,
Umesh

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.

Fixed in Manual versions 5.1+ by mysqldoc rev 35690.

Closed.