<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Row on FromDual GmbH</title><link>https://www.fromdual.com/tags/row/</link><description>Recent content in Row on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Thu, 12 Jan 2017 16:47:53 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/row/index.xml" rel="self" type="application/rss+xml"/><item><title>MySQL replication with filtering is dangerous</title><link>https://www.fromdual.com/blog/mysql-replication-with-filtering-is-dangerous/</link><pubDate>Thu, 12 Jan 2017 16:47:53 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-replication-with-filtering-is-dangerous/</guid><description>&lt;p&gt;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 &lt;code&gt;binlog_{do|ignore}_db&lt;/code&gt; settings), the binary log becomes incomplete and cannot be used for a proper Point-in-Time-Recovery. Therefore FromDual recommends AGAINST this approach.&lt;/p&gt;</description></item></channel></rss>