# PostgreSQL Replication and Ignition Redundancy

**URL:** <https://forum.inductiveautomation.com/t/postgresql-replication-and-ignition-redundancy/12298>\
**Category:** Ignition\
**Created:** [October 27, 2016, 3:45pm UTC](https://forum.inductiveautomation.com/t/postgresql-replication-and-ignition-redundancy/12298 "2016-10-27T15:45:33Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [December 11, 2017, 9:11pm UTC](https://forum.inductiveautomation.com/t/postgresql-replication-and-ignition-redundancy/12298/10 "2017-12-11T21:11:03Z")

</div>

I’m resurrecting this for a bit…

Anyone take a look at [Postgres-XL](https://www.postgres-xl.org/)?

I don’t know if I’d jump on it or not. It’s hard to find a balance between data integrity / availability, and how much management wants to spend to achieve it.

---

_[View the full topic](https://forum.inductiveautomation.com/t/postgresql-replication-and-ignition-redundancy/12298)._