Re: increasing HA - Mailing list pgsql-general

From Jehan-Guillaume (ioguix) de Rorthais
Subject Re: increasing HA
Date
Msg-id 20180905154429.6a0f8ccb@firost
Whole thread Raw
In response to Re: increasing HA  (Thomas Poty <thomas.poty@gmail.com>)
Responses Re: increasing HA  (Thomas Poty <thomas.poty@gmail.com>)
List pgsql-general
On Wed, 5 Sep 2018 15:06:21 +0200
Thomas Poty <thomas.poty@gmail.com> wrote:

> > In fact, PAF does not support slots. So it is not a good candidate if  
> > slot are a requirement.  
> Effectively slots are a requirement we prefer to keep

OK, so either patch PAF yourself (not recommended) or choose something
else. Note that two other ways are working with Pacemaker:
  * the pgsql resource agent (see FAQ of PAF)
  * a shared disk architecture (no pgsql replication)

> > > a proxy HAproxy and
> > > for fencincg, i am a bit disappointed, i don't know what to do/use  
> > Depend on your hardware or your virtualization technology.  
> Our production cluster (master and slave) runs on LXC container. Each LXC
> container runs on a HPE Blade Server. The storage is on a SAN 3PAR array.
> Any advice ?

I suppose you could find fencing agents for:

* the blade itself, but it would fence all the container running on it
* the access to the SAN from the failing container

I don't know if fencing agent exists for a container itself. Note that I'm not
familiar with the container world, I lack a lot of knowledge on this
technology.

++


pgsql-general by date:

Previous
From: Alessandro Gherardi
Date:
Subject: Re: scram-sha-256 authentication broken in FIPS mode
Next
From: Adrian Klaver
Date:
Subject: Re: unaccent(text) fails depending on search_path (WAS: pg_upgradefails saying function unaccent(text) doesn't exist)