pgEdge Distributed PostgreSQL

pgEdge Distributed PostgreSQL helps companies achieve high availability and reduced data latency, all while ensuring that data that must stay local remains local. Only pgEdge is multi-master, multi-region and multi-cloud, while being fully based on standard Postgres and 100% open (source available).

pgEdge‘s Distributed PostgreSQL offers fully managed cloud or self-hosted options. Visit www.pgedge.com to download or learn more.

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-20

If you've ever wondered how to tell if a vendor is actually running in a manner that's compatible with standard , PG Scorecard (pgscorecard.com) is a great resource.

Michael Josephson talks about how it works along with why compatibility matters in this blog:

pgedge.com/blog/postgresql-com

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-18

With 17 came many substantial changes to how deployments are handled; notably, logical replication saw many enhancements that help companies achieve true high availability & distribution (even relating to system upgrades across major versions). Read about it, and see related blogs for PG17 updates introduced, in this blog from Ahsan Hadi:

pgedge.com/blog/preserving-rep

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-13

@lutindiscret Thank you for the welcome, and for letting us know!! We actually just rolled out some changes as of this morning and will be updating the links in our bio accordingly. The GitHub link is gone for now until the new link is up ✨

You can still self-host (free) on containers & VMs here, if interested: pgedge.com/get-started/contain

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-13

With 17 came many substantial changes to how deployments are handled; notably, logical replication saw many enhancements that help companies achieve true high availability & distribution (even relating to system upgrades across major versions). Read about it, and see related blogs for PG17 updates introduced, in this blog from Ahsan Hadi:

pgedge.com/blog/preserving-rep

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-11

Did you know you can self-host pgEdge Distributed Postgres? 100% source-available, 100% based on community PostgreSQL, it lets you deploy on most flavors of Linux in VMs, containers, bare metal, or a localhost sandbox.

Learn more: pgedge.com/get-started/contain

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-10

What is Point-in-Time-Recovery (PITR) really, in ? In this blog, Ibrar Ahmed discusses how PITR has improved over time, how it works, and how to plan for a successful implementation within .

Check it out: www.pgedge.com/blog/point-in-time-recovery-pitr-in-postgresql

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-06

Every Tuesday at 11:00am ET, join the pgEdge team for — all about mastering Distributed high availability, and edge-ready database solutions. Whether you’re scaling apps or seeking zero downtime, these sessions are packed with hands-on insights, real-world demos, and live Q&A with the experts.

Don’t miss out! Learn more here: hubs.la/Q03qbnT70

Join us on Tuesday at 11am ET here: hubs.la/Q03qbltY0

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-05

performance has improved exponentially since PG15, with critical changes such as basic support for logical replication to seamless failover slots, only being able to set basic thresholds for autovacuum vs. being adaptive, and limited parallel query support evolving to expanded parallel aggregates.

Get advanced performance tuning techniques for PG17 as well as details on what's changed since PG15 in this blog from Ibrar Ahmed:

pgedge.com/blog/postgresql-per

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-04

💥 Downtime isn’t an option.

In this new DZone article, learn how to proactively prepare your database for disaster recovery—ensuring high availability, data integrity, and business continuity.

🔗 Read now: hubs.la/Q03qGDPh0

For more information on pgEdge, visit: hubs.la/Q03qGHYs0

Check the PostgreSQL Log Files
Start by inspecting the log files. Typically, you'll find the log files in /var/log/postgresql/ or $PGDATA/pg_log. Within the log files, entry headers indicate the severity level of the log entry; for example:

Shell
1 ERROR: could not read block 128 in file "base/16384/12571": read only @ of 8192 bytes
2 PANIC: invalid page in block 42 of relation base/16384/16728
3 LOG: startup process (PID 1234) was terminated by signal 6: Aborted
4 FATAL: the database system is in recovery mode
pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-06-04

🎉 We’re honored to be named to the DBTA 100 2025: Companies That Matter Most in !

At pgEdge, we’re redefining what’s possible with highly available distributed —and it’s great to see that impact recognized.

Check out our inclusion ➡️ hubs.la/Q03qK8s70

pgEdge Distributed PostgreSQLpgEdgeDistributedPostgres
2025-05-30

Our goal is straightforward, really: to help the world understand the power of , at scale. Our team has worked with for decades. We specialize in creating solutions for , fully distributed PostgreSQL for high availability (& much more).

Check out our site to run fully distributed, multi-master Postgres on your own: pgedge.com/get-started/contain

You can also always get in touch or try pgEdge Cloud free for 30 days: pgedge.com/

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst