RE: increasing HA - Mailing list pgsql-general

From ROS Didier
Subject RE: increasing HA
Date
Msg-id 3f3568458e7a4dcdbee781b272900183@PCYINTPEXMU001.NEOPROD.EDF.FR
Whole thread Raw
In response to increasing HA  (Thomas Poty <thomas.poty@gmail.com>)
Responses Re: increasing HA  ("Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr>)
List pgsql-general

Hi

               I have made a lot of PostgreSQL High Availability tests (more than 20 by solution) and the two following products respond well to the need :

(1)    Repmgr (2ndQuadrant)

(2)    Pglookout (aiven)

 

About PAF, the product is hard to install and set up . It need a linux cluster and a system engineers team to use it.

 

Best Regards

 

cid:image002.png@01D14E0E.8515EB90


Didier ROS

Expertise SGBD

DS IT/IT DMA/Solutions Groupe EDF/Expertise Applicative - SGBD
Nanterre Picasso - E2 565D (aile nord-est)
32 Avenue Pablo Picasso
92000 Nanterre

 

De : thomas.poty@gmail.com [mailto:thomas.poty@gmail.com]
Envoyé : mardi 4 septembre 2018 16:59
À : pgsql-general@lists.postgresql.org
Objet : increasing HA

 

Hello,

 

I am looking after some advice about solution allowing to increase High availability?

 

Here is a bit of context :

 

I have an Master-Slave architecture

 - 1 master

 - 2 asynchronous slaves using replication slot

 - backup is made with barman using replication slot

 - Wal archiving is done towards barman server

 

I think 3 axes could be improved ( I am totaly novice with these):

 

- using of a proxy

 I found HAproxy.

 Could you advice any others solutions to explore or share your experience?

- using an automatick failover

 I found PAF
 Could you advice any others solutions to explore or share your experience?

- using a tool for fencing a failing node

Ideally, I aimagine to disable network traffic in I/O to prevent client connecting and exchange between backup server failling server + on postgesql server disable automatic restart of the service.

Could you share you experience about it?

 

- Maybe an other axe to explore ?

 

Thank you

 

Thomas


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.

Attachment

pgsql-general by date:

Previous
From: Thomas Poty
Date:
Subject: increasing HA
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Barman versus pgBackRest