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.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

Release announcement 2.0.7

on 19 May 2018

The maintenance release makes the multiprocess logging safe. Now each replica process logs in a separate file. The --full option now is working. Previously the option had no effect causing the maintenance to run always a conventional vacuum. This release fixes the issues reported in ticket #73 and #75 by pg_chameleon’s users. The bug reported in ticket #73 caused a wrong data type tokenisation when an alter table adds a column with options (e.

Continue reading

Release announcement 2.0.6

on 29 April 2018

The maintenance release 2.0.6 fixes a crash occurring when a new column is added on the source database with the default value NOW(). The maintenance introduced in the version 2.0.5 is now less aggressive. In particular the run_maintenance command now executes a conventional VACUUM on the source’s log tables, unless the switch --full is specified. In that case a VACUUM FULL is executed. The detach has been disabled and may be completely removed in the future releases because very fragile and prone to errors.

Continue reading

Release announcement 2.0.5

on 25 March 2018

The maintenance release 2.0.5 a regression which prevented some tables to be synced with sync_tables when the parameter limit_tables was set. Previously having two or more schemas mapped with only one schema listed in limit_tables prevented the other schema’s tables to be synchronised with sync_tables. This release add two new commands to improve the general performance and the management. The command stop_all_replicas stops all the running sources within the target postgresql database.

Continue reading