| From: | "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr> |
|---|---|
| To: | AI Rumman <rummandba(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres Automated Failover |
| Date: | 2019-01-17 14:06:44 |
| Message-ID: | 20190117150644.78fdf8fc@firost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 17 Jan 2019 08:32:48 -0500
AI Rumman <rummandba(at)gmail(dot)com> wrote:
> Hi,
>
> I am planning to use Postgresql with TimescaleDb extension. I have to
> design a system similar to AWS RDS which supports automated failover,
> transparent minor version upgrades etc.
> In early days, I worked with PgPool II to enable heartbeat between the
> Postgres servers. Is there any new tool to achieve the same by which I can
> design a transparent failover system for Postgres?
There is multiple HA solutions, none are "transparent failover" though. They
are just automated-failover. A rollback-ed transaction because of failover will
never be transparent from the application point of view.
Look at Patroni or PAF, depending on what you want to achieve.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume (ioguix) de Rorthais | 2019-01-17 14:12:56 | Re: Barman versus pgBackRest |
| Previous Message | Deepika S Gowda | 2019-01-17 13:58:24 | Re: Postgres Automated Failover |