The bugfix release 2.0.3 fixes the issue #63 changing all the fields i_binlog_position to bigint. Previously binlog files larger than 2GB would cause an integer overflow during the phase of write rows in the PostgreSQL database. The issue can affect also MySQL databases with smaller max_binlog_size as it seems that this value is a soft limit. As this change requires a replica catalogue upgrade is very important to follow the upgrade instructions provided below.
This bugfix relase adds a missing functionality which wasn’t added during the application development and fixes a bug in the sync_tables command. Previously the parameter batch_retention was ignored making the replayed batches to accumulate in the table sch_chameleon.t_replica_batch with the conseguent performance degradation over time. This release solves the issue re enabling the batch_retention. Please note that after upgrading there will be an initial replay lag building. This is normal as the first cleanup will have to remove a lot of rows.
The first maintenance release of pg_chameleon v2 adds a performance improvement in the read replica process when the variables limit_tables or skip_tables are set. Previously all the rows were read from the replica stream as the BinLogStreamReader do not allow the usage of the tables in the form of schema_name.table_name. This caused a large amount of useless data hitting the replica log tables as reported in the issue #58.
The version 2.0 of pg_chameleon the MySQL to PostgreSQL replica system is now available. Several improvements come with this new milestone which is compatible with python 3.3+. Replicates multiple MySQL schemas within the same MySQL cluster into a target PostgreSQL database. The source and target schema names can be different. Conservative approach to the replica. Tables which generate errors are automatically excluded from the replica. Daemonised init_replica,refresh_schema,sync_tables processes. Daemonised replica process with two separated subprocess, one for the read and one for the replay.