Is there any drawback of MIXED replication mode?
-
10-12-2020 - |
Question
So, recent mysql server allows three types of replication mode: STATEMENT, ROW, MIXED. They all have pros/cons, and I pick the mode according to site characteristics.
When I get a replication error I sometimes need to examine the binlog files using mysqlbinlog
, so I tend to use MIXED mode. ROW based replication doesn't let you see it because contents is not very readable. I'm thinking MIXED mode is 'best of both worlds'.
I haven't yet seen a lot of discussion regarding MIXED mode, much less drawbacks of using it. Can someone tell me few reasons to be cautious?
Solution
Here are some disadvantages
- For you MyISAM users out there, concurrent inserts are prohibited.
- Data changes cannot be read unless you use mysqlbinlog with the options --base64-output=DECODE-ROWS and --verbose.
- BLOB data is written "as is" rather than the SQL that created the BLOB
- For more information, see the MySQL Documentation
Licensed under: CC-BY-SA with attribution
Not affiliated with dba.stackexchange