MySQL Configuration for Heterogeneous Deployments
The following are required for replication to heterogeneous targets to ensure that MySQL has been configured and generating row change information correctly:
MySQL must be using Row-based replication for information to be replicated to heterogenous targets. For the best results, you should change the global binary log format, ideally in the configuration file (
my.cnf):binlog-format = rowAlternatively, the global binlog format can be changed by executing the following statement:
mysql> SET GLOBAL binlog-format = ROW;For MySQL 5.6.2 and later, you must enable full row log images:
binlog-row-image = fullThis information will be forgotten when the MySQL server is restarted; placing the configuration in the
my.cnffile will ensure this option is permanently enabled.Table format should be updated to UTF8 by updating the MySQL configuration (
my.cnf):character-set-server=utf8collation-server=utf8_general_ciTables must also be configured as UTF8 tables, and existing tables should be updated to UTF8 support before they are replicated to prevent character set corruption issues.
To prevent timezone configuration storing zone adjusted values and exporting this information to the binary log and PostgreSQL, fix the timezone configuration to use UTC within the configuration file (
my.cnf):default-time-zone='+00:00'