Brandon Nesterenko via developers <[email protected]> writes:
> Indeed I think you are right. When writing the ticket, I was thinking > the binlog-in-engine implementation would bypass the pending rows event > and have its own cache that it monitored to write out-of-bounds > chunks live. I recall you mentioning getting rid of the pending rows > event last September in Helsinki (though I think you meant generally). > But if it uses the pending data and same binlog transaction cache, then > it should already be supported (though we need to test this). Aha, cool. Agree, should be tested. - Kristian. _______________________________________________ developers mailing list -- [email protected] To unsubscribe send an email to [email protected]
