Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by victor9000 on Thursday October 09, 2025 @10:30PM
(#45534920)
What failure cases did you encounter?
Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by pgedge_postgres on Thursday October 09, 2025 @10:50PM
(#45534996)
Getting some examples of real-world cases to share and will comment back with them ASAP; in the meantime, would you mind sharing what undocumented edge cases you came across and what solutions you explored to handle them? It would help with sharing super relevant use cases :-)
Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by verelo on Friday October 10, 2025 @12:48PM
(#45540984)
I tried to escape this world as quickly as possible, realizing how horrible it was, but the largest issue I ran into was around IO. Creating an environment that was highly tolerant to fault while having little to no replication delay meant checking in on the master database frequently. Keeping in mind this was around 2010 I found that the IO load on these databases was substantially larger than any database that i had ever worked on before. Things like available file handlers and other related performance problems came up more frequently than I’ve ever experienced before and frankly more frequently than I’ve ever experienced since.
If I was to summarize it, I would just say the performance characteristics were not something I was used to experiencing and often they would surprise me when they occurred, which meant having a good quality of a while for running this application was very challenging.
Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by pgedge_postgres on Thursday October 09, 2025 @11:22PM
(#45535118)
Just a guess, but some of the undocumented edge cases you saw might be explored in this blog from one of our software engineers, Shaun Thomas. It's all about conflict resolution & avoidance in PostgreSQL, in general: https://www.pgedge.com/blog/living-on-the-edge
If understanding how conflicts are handled in pgEdge is helpful, here's a link to the docs on the subject: https://docs.pgedge.com/spock_ext/conflicts
And the FAQ also delves into it some: https://www.pgedge.com/resources/faq
Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by baq on Friday October 10, 2025 @01:36AM
(#45535625)
Typical use case would be a anyone who has global presence, but serves users in particular geos (think AWS): you want a global user database but it’s soooo convenient to be able to join with regional data in a single query.
Re:Show HN: 100% open source, logical multi-master PostgreSQ...
by jwr on Friday October 10, 2025 @06:09AM
(#45537130)
> edge cases that can come up and they scare me off
They should! Read some of the excellent Jepsen analyses to see how scary things can be: https://jepsen.io/analyses
Many many years ago I worked on a monitoring tool that itself needed to be highly available, and we needed a solution like this. Ever since that time I've done everything in my power to avoid it.
What are the real world cases you built this for? And how can someone like me who has been bruised by past experiences get comfortable with it?