In a PostgreSQL database, sequences provide a convenient way to generate a unique identifier, and are often used for key generation. From the community, PostgreSQL provides functions and SQL language to help manage sequence generation, but the sequences themselves are not without limitations in a multi-master environment.

pgEdge, a powerful distributed database that leverages Equinix Metal's regionalized infrastructure to bring data closer to your users, resulting in lightning-fast application responsiveness regardless of where users are located. 

This is the second blog of a two blog series. In this post,  I will be talking about PostgreSQL clustering solutions that are based on logical replication.

In this post, we’ll investigate using Cloudflare Workers and pgEdge distributed PostgreSQL to build a web application with data access times kept to less than 100 ms, for users anywhere in the United States and Europe. Building web applications to be fast matters, and it generally doesn’t happen by accident. Let’s see if we can make it happen.

A number of distributed database vendors make claims about being “Postgres compatible” or “Postgres based”.  This is no doubt a response to the growing and overwhelming popularity of Postgres with developers.

With the release of pgEdge Cloud Developer Edition Preview, we’re particularly excited about getting distributed Postgres in the hands of more developers. We think edge computing platforms like Cloudflare Workers® pair nicely with a Postgres database located geographically close to the end user, and we’re excited to see what folks will build with the power of these platforms together.

About a year ago, I joined pgEdge because the mission of making applications faster and more reliable using distributed Postgres really clicked with me.

This blog is divided into two parts. In this section, we walk through how the logical replication feature has evolved over the years, what the recent improvements for logical replication are, and how the feature will likely change in the future. The second blog of the series will discuss the multi-active, multi-region, and highly available PostgreSQL cluster created by pgEdge that is built on top of logical replication and pglogical.  

pgEdge is an Equinix Metal database partner, and is now featured in the Equinix solution showcase.

how to optimize individual node performance when running pgEdge Platform on Amazon EC2 instances, and how do you achieve IOPs performance comparable with Amazon’s RDS.

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.