Pg-chameleon

..........................................................
* Fix wrong check for the next auto maintenance run if the maintenance wasn't run before
* Improve the replay function's speed
* Remove blocking from the GTID operational mode

..........................................................
* Add support for skip events as requested in issue 76. Is now possible to skip events (insert,delete,update) for single tables or for entire schemas.
* **EXPERIMENTAL** support for the GTID. When configured on MySQL or Percona server pg_chameleon will use the GTID to auto position the replica stream. Mariadb is not supported by this change.
* ALTER TABLE RENAME is now correctly parsed and executed
* Add horrible hack to ALTER TABLE MODIFY. Previously modify with default values would parse wrongly and fail when translating to PostgreSQL dialect
* Disable erroring the source when running with ``--debug`` switch enabled
* Add cleanup for logged events when refreshing schema and syncing tables. previously spurious logged events could lead to primary key violations when syncing single tables or refreshing single schemas.

..........................................................
* Fix for issue 71, make the multiprocess logging safe. Now each replica process logs in a separate file
* Fix the ``--full`` option to store true instead of false. Previously the option had no effect.
* Add `auto_maintenance` optional parameter to trigger a vacuum over the log tables after a specific timeout
* Fix for issue 75, avoid the wrong conversion to string for None keys when cleaning up malformed rows during the init replica and replica process
* Fix for issue 73, fix for wrong data type tokenisation when an alter table adds a column with options (e.g. ``ADD COLUMN foo DEFAULT NULL``)
* Fix wrong TRUNCATE TABLE tokenisation if the statement specifies the table with the schema.

..........................................................
* fix for issue 69 add source's optional parameter ``on_error_read:`` to allow the read process to continue in case of connection issues with the source database (e.g. MySQL in maintenance)
* remove the detach partition during the maintenance process as this proved to be a very fragile approach
* add switch ``--full`` to run a ``VACUUM FULL`` during the maintenance
* when running the maintentenance execute a ``VACUUM`` instead of a ``VACUUM FULL``
* fix for issue 68. fallback to ``binlog_row_image=FULL`` if the parameter is missing in mysql 5.5.
* add cleanup for default value ``NOW()`` when adding a new column with ``ALTER TABLE``
* allow ``enable_replica`` to reset the source status in the case of a catalogue version mismatch

..........................................................
* fix wrong exclusion when running sync_tables with limit_tables set
* add `run_maintenance` command to perform a VACUUM FULL on the source's log tables
* add `stop_all_replicas` command to stop all the running sources within the target postgresql database

..........................................................
* Fix regression added in 2.0.3 when handling MODIFY DDL
* Improved handling of dropped columns during the replica