From: | AI Rumman <rummandba(at)gmail(dot)com> |
---|---|
To: | "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres Automated Failover |
Date: | 2019-01-17 18:01:52 |
Message-ID: | CAGoODpf2adL-L-cwCx9HiW=g5-AmiFbsw9yyEY_bWvq2JbMFJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks, I'll check it out.
On Thu, Jan 17, 2019 at 9:06 AM Jehan-Guillaume (ioguix) de Rorthais <
ioguix(at)free(dot)fr> wrote:
> 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 | Rich Shepard | 2019-01-17 18:04:02 | Re: Refining query statement |
Previous Message | Rich Shepard | 2019-01-17 18:01:09 | Re: Refining query statement |