(github.com)

131 points pgedge_postgres | 1 comments | 09 Oct 25 22:53 UTC | HN request time: 0.422s | source

Show context

verelo ◴[10 Oct 25 00:05 UTC] No.45534285[source]▶

Interesting, i always see attempts to make these types of database tools as super interesting but then I think about all the undocumented edge cases that can come up and they scare me off.

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?

replies(6): >>45534920 #>>45534996 #>>45535118 #>>45535625 #>>45537130 #>>45537140 #

1. pgedge_postgres ◴[10 Oct 25 03:22 UTC] No.45535118[source]▶

>>45534285 #

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

↑

Show HN: Open source, logical multi-master PostgreSQL replication