Postgres Automated Failover

There is postgres multimaster replication. Please explore bdr multi master
node.

On Thu, Jan 17, 2019 at 7:03 PM AI Rumman <rummandba@gmail.com> wrote:

On Thu, 17 Jan 2019 08:32:48 -0500
AI Rumman <rummandba@gmail.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.

Hi,

In my opinion repmgr it's worth a look.

https://repmgr.org/

regards,

fabio pardi

Hi
For PostgreSQL Automatic Failover , we are using repmgr too.

Best Regards

Didier ROS
Expertise SGBD
DS IT/IT DMA/Solutions Groupe EDF/Expertise Applicative - SGBD

-----Message d'origine-----
De : f.pardi@portavita.eu [mailto:f.pardi@portavita.eu]
Envoyé : jeudi 17 janvier 2019 15:29
À : pgsql-general@lists.postgresql.org
Objet : Re: Postgres Automated Failover

Hi,

In my opinion repmgr it's worth a look.

https://repmgr.org/

regards,

fabio pardi

On 17/01/2019 14:32, AI Rumman 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?

Also is there any multi-master Postgresql solution? Is Postgres-XC production ready?

Any suggestions is appreciated. 

Thanks.

Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.

Thanks, I'll check it out.

On Thu, Jan 17, 2019 at 9:06 AM Jehan-Guillaume (ioguix) de Rorthais <
ioguix@free.fr> wrote: