Thanks for flagging this. You’re right that the issue sat too long without a response, and that’s on us. We’ve now replied on GitHub and are actively looking into it. It appears the crash may be related to CPU feature mismatches (e.g. missing AVX support when using pgvector), especially in emulated environments like ARM Macs running x86 containers. We’ve asked for system details to help confirm. Happy to dig in and resolve it quickly from here.
I think it’s great they’re opening it up. I hope they have a plan to defend when the hyperscalers show up to pillage beyond providing cloud containers and VMs as a paid service.
They really need to dial back on marketing bs.
async multimaster takes away consistency.
Piling on NewSQL DBS for slow synchronous writes to a quorum of nodes WTF?
async multi-master does trade off consistency for availability and latency. In PACELC terms, pgEdge leans into AP/EL, not CP. It’s built for low-latency local writes across regions, with built-in conflict resolution to manage eventual consistency. Definitely not trying to be a NewSQL quorum-write system. Just a different use case.
Thanks for the feedback! We're pretty excited about it, too :-)
Citus focuses on scaling Postgres via sharding, typically with a single write node and many read replicas. It’s great for high-throughput, analytical workloads. pgEdge, by contrast, is built for geo-distributed, multi-master Postgres — all nodes are writable, with built-in conflict resolution. It prioritizes low latency, availability, and data locality over pure scale-out. So the goals are pretty different.
pgEdge came about from a pglogical foundation, actually! from one of our blogs:
> pgEdge emerged in late 2024 as a serverless distributed Postgres managed cloud service, delivering low latency and high availability in three minutes or less. The pgEdge Platform (for on-premises distributed PostgreSQL) as well as pgEdge Cloud (for deploying in the cloud) was largely inspired by the original capabilities of the pgLogical extension.
20 comments
[ 2.5 ms ] story [ 43.7 ms ] threadTo configure passwordless sudo, open the /etc/sudoers file, and add a line of the form: %username ALL = (ALL) NOPASSWD: ALL
And the same user should have a password less SSH access with private key ...
Citus focuses on scaling Postgres via sharding, typically with a single write node and many read replicas. It’s great for high-throughput, analytical workloads. pgEdge, by contrast, is built for geo-distributed, multi-master Postgres — all nodes are writable, with built-in conflict resolution. It prioritizes low latency, availability, and data locality over pure scale-out. So the goals are pretty different.
I assume given there are two Vitess for Postgres being worked on now they have decided to open source it?
> pgEdge emerged in late 2024 as a serverless distributed Postgres managed cloud service, delivering low latency and high availability in three minutes or less. The pgEdge Platform (for on-premises distributed PostgreSQL) as well as pgEdge Cloud (for deploying in the cloud) was largely inspired by the original capabilities of the pgLogical extension.
https://www.pgedge.com/blog/navigating-distributed-postgresq...