Release announcement 2.0.21
https://codeberg.org/the4thdoctor/pg_chameleon/releases/edit/v2.0.21
This release comes with the following fixes and improvements.
Release announcement 2.0.14
This maintenance release improves the support for spatial datatypes.
Release announcement 2.0.13
This maintenance release adds the EXPERIMENTAL support for Point datatype thanks to the contribution by @jovankricka-everon.
Release announcement 2.0.12
This maintenance release fixes the issue #96 where the replica initialisation failed on MySQL 8 because of the wrong field names pulled out from the information_schema. Thanks to daniel-qcode for contributing with his fix.
Release announcement 2.0.11
This maintenance release fixes few things. As reported in issue #95 the yaml files were not completely valid. Thanks to rebtoor which fixed them.
Release announcement 2.0.10
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.
Release announcement 2.0.9
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.
Release announcement 2.0.8
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.
Release announcement 2.0.7
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.
Release announcement 2.0.6
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.