Open-source multi-master PostgreSQL replication is getting real attention. Spock from pgEdge promises logical multi-master replication for PostgreSQL and has sparked a live debate: can OSS scale horizontally like cloud-native distributed SQL? [1]
What Spock promises — At its core, Spock enables open, logical multi-master replication for PostgreSQL. [1]
Edge cases and real-world concerns — The discussion centers on undocumented issues, conflict resolution, and how teams handle conflicts in practice. IO load and the need to keep the master database tamed while maintaining low replication delay come up as practical pain points. [1]
• Edge cases and conflict resolution — conflicts handling is a focus in the ongoing discussions and in related resources. [1] • IO and performance realities — the smallest misstep can blow up monitoring and resources due to higher IO pressures. [1]
Use cases and scope — A typical use case is global presence: serving users across geos and joining regional data in a single query. That regional-global mix is what proponents tout as Spock’s sweet spot. [1]
Docs and resources — There are docs on conflicts and a FAQ that teams reference as they navigate trade-offs and integration questions. [1]
Closing thought — The debate isn’t settled. Spock raises big questions about horizontal scale, conflict handling, and how far open-source PostgreSQL can go in practice. [1]
References
Show HN: Open source, logical multi-master PostgreSQL replication
Discusses pgEdge Spock multi-master PostgreSQL replication, conflict resolution, edge cases, and comparisons to CockroachDB, MySQL, Aurora, Spanner; CAP; DDL concerns.
View source