# SQL replication capability for temporal postgres db

**URL:** <https://community.temporal.io/t/sql-replication-capability-for-temporal-postgres-db/4293>\
**Category:** Community Support\
**Tags:** java-sdk, mysql, database, configuration, replication\
**Created:** [March 28, 2022, 9:36am UTC](https://community.temporal.io/t/sql-replication-capability-for-temporal-postgres-db/4293 "2022-03-28T09:36:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [March 28, 2022, 5:19pm UTC](https://community.temporal.io/t/sql-replication-capability-for-temporal-postgres-db/4293/4 "2022-03-28T17:19:28Z")

</div>

For MySQL/PostgreSQL, either make sure DB layer replication is strong consistent, or try not to use it. Temporal depends on DB being strong consistent. The replication strategy you chose needs to be sync. Async DB replication will cause data loss and inconsistencies.

Temporal includes the [multi-cluster replication feature](https://docs.temporal.io/docs/server/multi-cluster) because it cannot always rely on DB replication for some of the supported DBs (nature of DB, not Temporal).

---

_[View the full topic](https://community.temporal.io/t/sql-replication-capability-for-temporal-postgres-db/4293)._