pgedge_postgres

7 ms·

31.
Building a RAG Server with PostgreSQL – Part 1: Loading Your Content(pgedge.com)
1 points by pgedge_postgres 10mo ago|0 comments
32.
Postgres 18: Skip Scan – Breaking Free from the Left-Most Index Limitation(pgedge.com)
1 points by pgedge_postgres 10mo ago|0 comments
33.
Show HN: PgEdge Control Plane, a declarative API for multi-region Postgres mgmt(github.com)
5 points by pgedge_postgres 11mo ago|0 comments
34.
Simplifying Cluster-Wide PostgreSQL Execution with Exec_node() and Spock OSS(pgedge.com)
10 points by pgedge_postgres 11mo ago|1 comments
35.
Pg_statviz 0.8 (timeseries analysis of Postgres internal stats) released(vyruss.org)
1 points by pgedge_postgres 11mo ago|1 comments
36.
by pgedge_postgres 11mo ago
Now with PostgreSQL 18 support.
37.
Reinventing PostgreSQL for the Next Generation of Apps(thenewstack.io)
1 points by pgedge_postgres 11mo ago|0 comments
38.
Show HN: Deploy Distributed PostgreSQL on K8s with CloudNativePG, Helm, + PgEdge(github.com)
1 points by pgedge_postgres 11mo ago|0 comments
39.
PgEdge and CloudNativePG Partnership: Simplifying Distributed Postgres on K8s(pgedge.com)
2 points by pgedge_postgres 11mo ago|0 comments
40.
by pgedge_postgres 1y ago
It technically is source-available, as of Nov 2024, anyway: https://news.itsfoss.com/cockcroachdb-no-open-source/ So yes, license (and compatibility - see https://pgscorecard.com ) are two major differences
41.
by pgedge_postgres 1y ago
You're actually 100% correct! CockroachDB is only 57.25% compatible with standard PostgreSQL (according to https://pgscorecard.com , which details the way it comes up with these numbers) whereas we are 100% compatible (and 1
42.
by pgedge_postgres 1y ago
There's a lot of ways to approach the common problems found when running multi-master / active-active PostgreSQL. (A complete guide on this, specifically using PostgreSQL in general , was written by one of our solutions engineers
43.
by pgedge_postgres 1y ago
Just a guess, but some of the undocumented edge cases you saw might be explored in this blog from one of our software engineers, Shaun Thomas. It's all about conflict resolution & avoidance in PostgreSQL, in general: https:/&
44.
by pgedge_postgres 1y ago
As a note, there's also specific documentation regarding this: https://docs.pgedge.com/spock_ext/conflicts And, one of our solutions engineers (Paul Rothrock) has a video released a month ago on this topic as well
45.
by pgedge_postgres 1y ago
The official FAQ has a good amount of info on how conflict resolution is handled ( https://www.pgedge.com/resources/faq )! Relevant excerpt: "pgEdge offers eventual consistency between nodes using a configurable pol
46.
by pgedge_postgres 1y ago
We're not claiming to be a new idea, by any means :-) Unfortunately, Bucardo is no longer being updated. Our goal is simply to support continued innovation of distributed PostgreSQL along with similar tools for enabling high availabili
47.
by pgedge_postgres 1y ago
Getting some examples of real-world cases to share and will comment back with them ASAP; in the meantime, would you mind sharing what undocumented edge cases you came across and what solutions you explored to handle them? It would help with
48.
by pgedge_postgres 1y ago
Thanks for pointing out the lack of info on conflict resolution in the README! It's been reported and we'll look at getting that updated ASAP. In the meantime, you can find a lot of information in the official FAQ on how conflict
49.
Show HN: Open source, logical multi-master PostgreSQL replication(github.com)
151 points by pgedge_postgres 1y ago|60 comments
50.
PgEdge Enterprise Postgres and Full Commitment to Open Source(pgedge.com)
2 points by pgedge_postgres 1y ago|0 comments
51.
Distributed Postgres Solves Cloud's High-Availability Problem(thenewstack.io)
2 points by pgedge_postgres 1y ago|0 comments
52.
by pgedge_postgres 1y ago
the 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
53.
by pgedge_postgres 1y ago
We're a little different in that we're not just 100% open-source, but also 100% compatible with community PostgreSQL. see https://pgscorecard.com for comparisons between pgEdge and YugabyteDB, CockroachDB on that front
54.
by pgedge_postgres 1y ago
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 le
55.
by pgedge_postgres 1y ago
agreed!! :-)
56.
by pgedge_postgres 1y ago
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
57.
by pgedge_postgres 1y ago
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
58.
by pgedge_postgres 1y ago
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. missi
59.
by pgedge_postgres 1y ago
We definitely really appreciate how open source leads to real innovation and actually useful code; no intention of openwashing here. Thank you for noticing that :-)