Binary Log on FromDual GmbH

Traffic mirroring with MariaDB MaxScale

oli.sennhauser@fromdual.com (Oli Sennhauser) — Thu, 24 Dec 2020 16:27:33 +0000

Recently we had the case that a customer claimed that MariaDB 10.3 Binary Log is using 150% more space on disk than MySQL 5.7 Binary Log. Because I never observed something similar, but to be honest, I did not look to intensively for this situation, we had to do some clarifications.

MySQL replication with filtering is dangerous

oli.sennhauser@fromdual.com (Oli Sennhauser) — Thu, 12 Jan 2017 16:47:53 +0000

From time to time we see in customer engagements that MySQL Master/Slave replication is set-up doing schema or table level replication filtering. This can be done either on Master or on Slave. If filtering is done on the Master (by the binlog_{do|ignore}_db settings), the binary log becomes incomplete and cannot be used for a proper Point-in-Time-Recovery. Therefore FromDual recommends AGAINST this approach.

Binlog format MIXED with filtering

oli.sennhauser@fromdual.com (Oli Sennhauser) — Wed, 15 Jul 2015 06:11:36 +0000

Binlog format MIXED changes the binary log format (ROW or STATEMENT) depending on the queries (deterministic or not). This makes it impossible to define 100% correctly working binary log filter rules.

Oops! - That SQL Query was not intended... Flashback

oli.sennhauser@fromdual.com (Oli Sennhauser) — Mon, 24 Jun 2019 14:12:00 +0200

It is Saturday night at 23:19. Time to go to bed after a hard migration day. Just a last clean-up query before finishing: Tap tap tap. Enter! - Oops!