Bug #14722 RBR: slave writes nothing to General Query Log when executing RBR events
Submitted: 7 Nov 2005 20:55 Modified: 15 Oct 2008 16:25
Reporter: Guilhem Bichot Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.0-wl1012 OS:Any (ALL)
Assigned to: Mats Kindahl CPU Architecture:Any

[7 Nov 2005 20:55] Guilhem Bichot
It's an open question: should a trace of the RBR events be put into the General Query Log?
As in statement-based replication, the replicated statements (i.e. the executed Query events) are in the General Query Log, the RBR events could as well be there in some abbreviated form. The General Query Log is supposed to contain a trace of all work done by the server.

They should not be logged if the table is ignored (like in statement-based replication).

How to repeat:
run any rpl_row_* test and look into var/log/slave.log for RBR events.
[30 Jan 2006 8:54] Mats Kindahl
It is uncertain if any customer require this feature, so we close this bug for now. If any requests for this feature arrives from a customer, we can open the bug again.
[25 Jul 2013 0:34] Justin Swanhart
I would like this reopened.  I'm not a customer but a community user and I think that 5.6 RBR should log the query event for an RBR even when available.