Details
-
Task
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
Hello,
I couldn't find if that was ever discussed before...
I'd like to propose a feature of ignoring a certain table(s) activity being written to binlog.
This can save on traffic + ease on slaves that need to replicate just few tables but have to download gigabytes of binary logs and slow down because replaying it takes time.
So maybe instead of ignoring certain tables on slave it's possible to let the master avoid creating binlog with it?
At this moment I have to manipulate with rewrite-db to let something replicate to a different database and avoid that db from appearing in binlogs. Probably this won't work with statement log format, but row replication should do the thing imo. Anyway this can be left to dba/sysadmin to decide
Hope you find it interesting and possible to implement
Thanks!
Alex
p.s. alternatively it could be a feature for maxscale binlog proxy to let certain slaves download only relevant parts..or something like that