postgresql_cluster
pg_auto_failover
postgresql_cluster | pg_auto_failover | |
---|---|---|
9 | 14 | |
1,272 | 1,036 | |
- | 0.7% | |
9.0 | 6.4 | |
7 days ago | 3 months ago | |
Jinja | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
postgresql_cluster
-
Automated Deployment of PostgreSQL Ha Clusters Anywhere
Creating a robust and reliable database cluster is often fraught with challenges.A manual deployment process can be fraught with risks, particularly for those who lack extensive experience. Even minor errors in configuration can drastically affect your database's performance and stability.
Recognizing this intricacy, many businesses choose to use cloud-based managed databases. These services offer convenience but not without limitations. These drawbacks can include being tied to a specific cloud provider and limited direct access to the database server for adjustments. These constraints can hinder your ability to tune your system and perform thorough performance analyses.
In response to these challenges, we've developed a project to make this process easier and more efficient. This project uses automation to streamline the deployment of High-Availability PostgreSQL Clusters. By doing so, it helps mitigate the risks involved with manual configuration and speeds up the deployment process.
Our solution caters to various deployment environments. It allows you to establish your cluster either in your own data center or in the cloud, providing a robust database solution similar to managed databases, but with you retaining full control.
Explore the project here: https://github.com/vitabaks/postgresql_cluster
-
Docker: Patroni + HAProxy + Etcd + PgBouncer
FYI: postgresql_cluster
-
Can someone share experience configuring Highly Available PgSQL?
HA postgres
- Toying with the idea of running Postgres instead of using RDS
- HaProxy/PgBouncer location.
- PostgreSQL High-Availability Cluster
-
Ask HN: Tips on hosting your own Postgres instance
If not Kubernetes, check out this: https://github.com/vitabaks/postgresql_cluster – Postgres + patroni + pgBouncer + WAL-G or pgBackRest + Netdata + more, managed by Ansible.
If you do want to use Kubernetes, then check out StackGres.io and https://github.com/zalando/postgres-operator
-
PostgreSQL High availability
Also check PostgreSQL High-Availability Cluster (based on "Patroni" and "DCS(etcd)"). Automating deployment with Ansible.
pg_auto_failover
- 11 Years of Hosting a SaaS
- Streamlining High Availability in PostgreSQL, a Simpler Alternative
-
Why PostgreSQL High Availability Matters and How to Achieve It
pg_auto_failover makes it an absolute breeze. I cannot understand how it's not mentioned in the article.
I've been runnning it for 3 years with great success - https://github.com/hapostgres/pg_auto_failover/discussions/6...
-
Can someone share experience configuring Highly Available PgSQL?
Simplified and probably OK: pg_auto_failover - One Monitor/Witness node and minimum services otherwise. Good documentation to get started and not nearly as complex as Patroni.
-
PG redundancy even in majority failure
There are tools that make managing such a system easier. Check out patroni, pg_auto_failover or PAF
- Just Use Postgres for Everything
-
The C++ Asynchronous Framework
This is /extremely/ uncharitable. It depends more on the project.
For example, both Go and .NET are very well written with comprehensible documentation. Many projects have also been absorbed by the Apache Foundation or other FOSS initiatives.
Every FANG has boat loads of teams working on umpteen different open source packages. The quality naturally varies.
Let me pick two more esoteric projects as a point of comparison.
Yandex Odyssey (https://github.com/yandex/odyssey) an advanced multi-threaded PostgreSQL connection pooler and request router. Figuring out how exactly and when to use this is not quite clear. There is no "getting started" guide for this package. There is barely any explanation for how it works or what it does.
pg_auto_failover (https://github.com/citusdata/pg_auto_failover) run by Citus (owned by Microsoft) monitors and manages automated failover for a Postgres cluster. This repo even has diagrams explaining the workflow and complete instructions.
-
Do you use Percona Distribution for PostgreSQL? How is it working for you?
Right, https://github.com/citusdata/pg_auto_failover has been on my reading list
-
Simpler Postgresql replication setup (NO managed services)
My go to for this is https://github.com/citusdata/pg_auto_failover set up with ansible https://github.com/neuroforgede/pg\_auto\_failover\_ansible
-
pg_auto_failover ile PostgreSQL Cluster Kurulumu
pg_auto_failover github | readthedocs | ytube
What are some alternatives?
patroni - A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
citus - Distributed PostgreSQL as an extension
embedded-postgres - Run a real Postgres database locally on Linux, OSX or Windows as part of another Go application or test
orchestrator - MySQL replication topology management and HA
top500-benchmark - Automated Top500 benchmark for clusters or single nodes.
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
pigsty - Battery-Included PostgreSQL Distro as a Free RDS Alternative
discussion
k3s - Lightweight Kubernetes
tds_fdw - A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase and Microsoft SQL Server)