# PostgreSQL: pg\_chameleon 2.0.15

**URL:** <https://forum.devtalk.com/t/postgresql-pg-chameleon-2-0-15/2465>\
**Category:** Backend Official News\
**Tags:** postgres, other-news\
**Created:** [23 September 2020 07:01 UTC](https://forum.devtalk.com/t/postgresql-pg-chameleon-2-0-15/2465 "2020-09-23T07:01:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bot](https://forum.devtalk.com/user_avatar/forum.devtalk.com/bot/32/1112_2.png) [@bot](https://forum.devtalk.com/u/bot)\
**Post date:** [23 September 2020 07:01 UTC](https://forum.devtalk.com/t/postgresql-pg-chameleon-2-0-15/2465/1 "2020-09-23T07:01:53Z")

</div>

A new [PostgreSQL](https://devtalk.com/postgresql) blog post/announcement has been posted!

> [@](#):
>
> The new maintenance release for pg\_chameleon adds the support for reduced lock if MySQL engine is transactional, thanks to [rascalDan](https://github.com/rascalDan)
> 
> The initialisation process now checks whether the engine for the table is transactional and runs the initial copy within a transaction. The process still requires a FLUSH TABLES WITH READ LOCK but the lock is released as soon as the transaction snapshot is acquired. This improvement allows pg\_chameleon to run against primary databases with minimal impact during the init\_replica process.
> 
> The python-mysql-replication requirement is now changed to version \>=0.22 which adds the support for PyMySQL \>=0.10.0.

Get the full details here: [PostgreSQL: pg\_chameleon 2.0.15](https://www.postgresql.org/about/news/2078/)