6 ms·
PgEdge Goes Open Source
- fdefilippo 1y ago[dead]
- nik736 1y agoAnyone has any experience with PgEdge and can tell us about reliability? :-)
- Daril 1y agoI wanted to try it months ago ... but I stopped when I read in the install documentation : To 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 ...
- 0x6c6f6c 1y agoIt could do better for sure, but it's a just a Get Started guide, I never consider that a Production Ready guide.
- Valodim 1y agoHonest question, what's the problem with that? Hinging admin access for some machine on an ssh key seems like not too unusual practice?
- Daril 1y agoFrom a security point of view, I am not comfortable giving a user unlimited access to the server. I don't know what solution pgEdge is implementing, but granting full access to the server when it should only operate on PostgreSQL is a security concern for me.
- pgedge_postgres 1y agothe Getting Started guide is definitely a different mindset than what we would recommend for Production Ready, particularly if there's specific security requirements in mind. With that being said, it should be more clear, so we've reported this to our documentation team to make sure it is!
- emarsden 1y agoThey have an open issue concerning a SIGILL when loading the pgvector extension that hasn't been fixed or seen any activity in a month. https://github.com/pgEdge/pgedge-docker/issues/20
- pgedge_postgres 1y agoThanks 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.
- kstrauser 1y agoAnd under the PostgreSQL license, an actual OSI approved one, not a fake open source in name only monstrosity. Very nice!
- hxtk 1y agoIf you're referring to the post from yesterday, they actually relicensed it as Apache 2.0: https://news.ycombinator.com/item?id=45196173 https://news.ycombinator.com/item?id=45196173
- kstrauser 1y agoNo, I had in mind different recent announcements when companies selected closed licenses that let you look at the code but not actually use it, then bragged about open sourcing their project.
- DetroitThrow 1y agoAnnouncement title and actual license divergence has made reading these announcements a bit of a chore on HN since you're required now to read the full post. Good on these guys for not open washing their project. And of course it doesn't help the tedium of reading HN that there's 5 very vocal commentators who want to the world to know that "OSI doesn't own the definition of open source", even though when asked will define open source as "can be commercially restricted".
- pgedge_postgres 1y agoWe definitely really appreciate how open source leads to real innovation and actually useful code; no intention of openwashing here. Thank you for noticing that :-)
- tw04 1y agoI 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.
- atombender 1y agoWeird, I posted this yesterday, why didn't HN detect the duplicate? https://news.ycombinator.com/item?id=45203769 https://news.ycombinator.com/item?id=45203769
- WolfOliver 1y agoYour's has to little upvotes. I think it is only detected as duplicate if it had made the front page in the last few months.
- atombender 1y agoHm, I've had my submissions deduped before, where the existing post also had few upvotes and was definitely not on the front page.
- hu3 1y agosame
- darqis 1y agoI can't tell what it actually is. Too much marketing babble
- eXpl0it3r 1y ago> pgEdge is a modern distributed database system built on standard PostgreSQL that’s designed for geo-distribution, high availability, and low latency — especially useful for "edge" deployments. Had to look elsewhere as well...
- jmholla 1y agoAlso, in that same vein of caginess, they don't call out their pricing. It's one of those, "contact sales" services.
- benjiro 1y agoYugabyteDB / CockroachDB like from that description. Curios to see how it competes with multigres.
- pgedge_postgres 1y agoWe're a little different in that we're not just 100% open-source, but also 100% compatible with community PostgreSQL. see https://pgscorecard.com https://pgscorecard.com for comparisons between pgEdge and YugabyteDB, CockroachDB on that front. More thoughts on why we feel that's important here: https://www.pgedge.com/blog/considering-distributed-postgres-how-to-evaluate-vendor-claims-of-postgres-compatibility https://www.pgedge.com/blog/considering-distributed-postgres... and the Buyer's Guide (https://www.pgedge.com/landing-pages/distributed-postgresql-buyers-guide https://www.pgedge.com/landing-pages/distributed-postgresql-...) referenced within does list more technical details and comparisons between us and YugabyteDB / CockroachDB.
- qaq 1y agoThey 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?
- pgedge_postgres 1y agoasync 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.
- justinclift 1y agoThis is good news. :)
- pgedge_postgres 1y agoagreed!! :-)
- bigwheels 1y agoI appreciate the open source foundation! Is the goal of pgEdge functionally aligned or divergent from what CitusDB offers?
- pgedge_postgres 1y agoThanks 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.
- ksec 1y agoIs PgEdge Vitess of MySQL ? I assume given there are two Vitess for Postgres being worked on now they have decided to open source it?
- pgedge_postgres 1y agopgEdge 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. https://www.pgedge.com/blog/navigating-distributed-postgresql-options-pglogical-and-beyond https://www.pgedge.com/blog/navigating-distributed-postgresq...