According to a recent LinkedIn post from pgEdge Inc, internal testing of rolling upgrades between PostgreSQL 17 and 18 using its open-source Spock extension surfaced replication and configuration edge cases. The post describes a method of adding a PostgreSQL 18 node, shifting traffic, and retiring older nodes while maintaining a writable node throughout the process.
The company’s LinkedIn post highlights that certain replication issues did not appear in status checks, including tables not assigned to replication sets and failover flags on Spock slots, as well as interactions with Patroni configuration. This focus on operational reliability in multi-master logical replication suggests pgEdge is investing in robustness for high-availability database deployments, which may strengthen its appeal to enterprise users.
As shared in the post, the testing work and planned follow-up on failover scenarios indicate ongoing product refinement rather than a specific commercial launch. For investors, this activity points to continued R&D emphasis on complex distributed systems behavior, potentially enhancing pgEdge’s competitive position in multi-master PostgreSQL solutions over time.

