According to a recent LinkedIn post from pgEdge Inc, a technical walkthrough examines upgrading individual nodes in a three-node, multi-master PostgreSQL cluster in place, rather than adding replacement servers. The test used pgEdge’s open-source Spock 5.0.13 extension and moved one node from PostgreSQL 17.10 to 18.6, while Patroni managed a physical standby for high availability.
The post describes a failure mode in which an upgraded node appeared healthy to its peers but was not applying incoming changes. It attributes the issue to upgrade-state details not carried over by pg_upgrade and also flags Patroni system-ID checks, PostgreSQL 18’s default data checksums, and logical-slot considerations for upgrades from earlier versions.
For investors, the walkthrough suggests pgEdge is addressing operational risks in distributed database upgrades, an area relevant to organizations seeking high availability without provisioning extra infrastructure. If the documented procedures prove repeatable, they could support adoption of pgEdge’s replication and database-management technologies, although the post presents a technical test rather than evidence of revenue, customer growth, or broader commercial traction.

