From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Postgresql version of SQL Server Availability Groups? |
Date: | 2022-09-18 14:58:37 |
Message-ID: | dabdcc54-98fc-ed7f-4b7b-f504f9f7b732@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Currently my customer has some very large stand-alone PostgreSQL 9.6 (will
migrate next year to v13) databases, and they want to add HA.
Specifically, they want a "cluster name" which points to a Primary database
server's IP address, and and which automatically (presumably through through
a heartbeat and quorum voting system) points to a Secondary database
server's IP address if the Primary server goes down. Both servers are in
the same data center. (Replication would be handled by a standard PostgreSQL
method.)
This is *not* load balancing, but a purely HA solution.
I looked at HAProxy, but it seems to be focused on load balancing, while the
Patroni documentation does not seem to mention a cluster name.
Am I missing something?
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Licio Matos | 2022-09-18 19:23:04 | Re: Postgresql version of SQL Server Availability Groups? |
Previous Message | Stephen Frost | 2022-09-15 22:32:41 | Re: Ldap config for Active Directory |