PostgreSQL stands as a resilient and adaptable open-source relational database management system. In an era where data requirements constantly shift, organizations are increasingly delving into the realm of distributed databases to unlock scalability, enhance high availability, and boost overall performance.

High Availability (HA) encompasses a range of techniques and strategies designed to ensure uninterrupted access to databases for the longest feasible durations. Essentially, it's the system's capacity to maintain consistent operation, even when faced with the failure of one or more pivotal components. For applications deemed mission-critical, high availability is an indispensable requirement, rather than a mere luxury.

At pgEdge, we're thrilled to announce a significant milestone in our cloud journey. Building on our successful support for AWS and Azure, we are excited to extend our enterprise cloud solution to include Google Cloud. This expansion means that pgEdge Cloud can now cater to the vast majority of database workloads in the cloud, offering our users a comprehensive and secure experience across cloud providers.

In this blog, we will review the new features pgEdge Platform brings to the table and benefits of its multi-master capabilities.

In this blog post, we'll delve deep into the risks of not having a multi-region strategy for your PostgreSQL database system and explore why it's a game-changer in today's data-centric world.

With the release of PostgreSQL 16, the foundation for leveraging logical replication in active-active setups has significantly improved

In this blog we'll demonstrate how to configure pgVector with pgEdge to provide similarity search functionality across a pgEdge Distributed PostgreSQL cluster.  

Spock brings in a host of new features, including conflict resolution and avoidance, asynchronous replication, and more.

In this blog post, we will delve into the concept of multi-master PostgreSQL, the key benefits to this architecture, and why it is a critical solution for modern applications.

This blog covers new logical replication performance features added in PostgreSQL 16; stay tuned for more blogs discussing the remaining PostgreSQL 16 logical replication features.

The goal of this guide is to efficiently establish a local pgEdge cluster with two nodes using Docker Compose.

Thanks to all that joined our Webinar An Open Approach to Asynchronous Multi-master Replication With PostgreSQL! The webinar recording and details can be found here.

Today we are announcing support for multiple Postgres versions in pgEdge Distributed PostgreSQL, including the recently released PostgreSQL 16 Beta 1. 

Like many in the Postgres world we were excited to see in the just released Stack Overflow 2023 Developer Survey that Postgres is now the most used database across the 90,000+ developers surveyed.

PostgREST is a standalone web server to access your pgEdge Postgres database cluster with RESTful API calls...

In this post, we’ll investigate how to combine Cloudflare Workers with pgEdge’s distributed PostgreSQL database, allowing us to also locate the application’s data close to the end users.

In this post, I’ll focus on the improvements the community has added to logical replication for PostgreSQL 16.

Postgres Conference Silicon Valley (April 20 and 21, 2023) is now behind us. It was an exciting time with...

Typically, data replication in PostgreSQL is done between an active (primary) database and one or more...

Even though we are just coming out of stealth, Denis and I are already being asked why we started pgEdge, and why now. 

In his initial blog piece my longtime friend and 2-time co-founder Phillip Merrick talks about why we started pgEdge.  

In this post we discuss how developers working with edge platforms like Cloudflare Workers, Fastly Compute@Edge and Vercel.