Reminds me of this interesting call out in Postgres 16: The exciting and the unnoticed:
> Moving towards Active Active replication: A feature was committed in Postgres 16 to allow logical replication to avoid replication loops, which is when a transaction gets replicated from source to target and back. Postgres 16 allows subscribers to process only changes which have no origin which allows you to prevent these loops. Bi-directional active-active replication is still very complicated and requires solving a lot of problems, but this feature tackles one of those important sub-problems.
> pgactive is based on the open-source BDR project and includes functions that let you set up an active-active PostgreSQL cluster, conflict detection and automatic resolution methods (for example, last-write-wins), conflict monitoring, and more.
Reminds me of this interesting call out in Postgres 16: The exciting and the unnoticed:
> Moving towards Active Active replication: A feature was committed in Postgres 16 to allow logical replication to avoid replication loops, which is when a transaction gets replicated from source to target and back. Postgres 16 allows subscribers to process only changes which have no origin which allows you to prevent these loops. Bi-directional active-active replication is still very complicated and requires solving a lot of problems, but this feature tackles one of those important sub-problems.
https://tembo.io/blog/postgres-16/#laying-the-groundwork-for... https://news.ycombinator.com/item?id=37613690 (18d ago, 1 comment)
The AWS submission here is quite short. There's a longer read available at https://aws.amazon.com/blogs/database/using-pgactive-active-... that sheds some light on the basis for their technology:
> pgactive is based on the open-source BDR project and includes functions that let you set up an active-active PostgreSQL cluster, conflict detection and automatic resolution methods (for example, last-write-wins), conflict monitoring, and more.
They link to this old BDR project wiki page https://wiki.postgresql.org/wiki/BDR_Project , but it's quite stale. Efforts seems to have been ongoing as EnterpriseDB, https://github.com/EnterpriseDB .
That's many of the same folks as behind the cloudnative-pg k8s operator. https://www.enterprisedb.com/blog/introducing-cloudnativepg-... https://news.ycombinator.com/item?id=37616033 https://hn.algolia.com/?query=cloudnative-pg&sort=byDate