pg_chameleon replica system

pg_chameleon is a MySQL to PostgreSQL replica system written in Python 3. The tool can connect to the mysql replication protocol and replicate the data changes in PostgreSQL. Whether the user needs to setup a permanent replica between MySQL and PostgreSQL or perform an engine migration, pg_chamaleon is the perfect tool for the job.

Release announcement 2.0.11

on 25 October 2019

This maintenance release fixes few things. As reported in issue #95 the yaml files were not completely valid. Thanks to rebtoor which fixed them. clifff made a pull request to have the start_replica running in foreground when log_file set to stdout. Previously the process remained in background with the log set to stdout. As Travis seems to break down constantly the CI configuration is disabled until a fix or a different CI is found .

Continue reading

Release announcement 2.0.10

on 1 September 2018

This maintenance release fixes a regression caused by the new replay function with PostgreSQL 10. The unnested primary key was put in cartesian product with the json elements generating NULL identifiers which made the subsequent format function to fail. This release adds a workaround for decoding the keys in the mysql’s json fields. This allows the sytem to replicate the json data type as well. The command enable_replica fixes a race condition when the maintenance flag is not returned to false (e.

Continue reading

Release announcement 2.0.9

on 19 August 2018

This maintenance release fixes a wrong check for the next auto maintenance run if the maintenance wasn’t run before. Previously when changing the value of auto_maintenance from disabled to an interval, the process didn’t run the automatic maintenance unless a manual maintenance was executed before. This release adds improvements on the replay function’s speed. The new version is now replaying the data without accessing the parent log partition and the decoding logic has been simplified.

Continue reading

Release announcement 2.0.8

on 14 July 2018

This maintenance release adds the support for skip events. Is now is possible to skip events (insert,delete,update) for single tables or for entire schemas. A new optional source parameter skip_events: is available for the sources with type mysql. Under skip events there are three keys one per each DML operation. Is possible to list an entire schema or single tables in the form of schema.table. The example snippet disables the inserts on the table delphis_mediterranea.

Continue reading