Re: Setting up High Availability Group of PostgreSQL instances using RedHat Cluster Suite

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Terry Khatri *EXTERN*" <terrykhatri531(at)gmail(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Setting up High Availability Group of PostgreSQL instances using RedHat Cluster Suite
Date: 2012-12-03 10:32:10
Message-ID: D960CB61B694CF459DCFB4B0128514C208C99F87@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Terry Khatri wrote:
> I need to do the subject setup using PostgreSQL, where when one node
goes down another takes over
> without manual intervention, the way it is done in Oracle using grid
infrastructure and in SQL Server
> 2012 using their Alway-On feature
>
> My question is, has anyone done that ? can anyone please help me
implement it, I have googled on the
> subject, some people have done that and EnterpriseDB offer their
services to implement it but there
> are no details how actually to do it.
>
> Your step by step guide will be much appreciated.

No step-by-step guide, but we have had such a configuration
running for years.

One gotcha I remember was that we had to modify
/usr/share/cluster/postgres.sh to wait for a while
if the regular checks got
FATAL: the database system is starting up
because otherwise you could end up with a disabled
service after a failover (+ crash recovery).

We had a 2 node cluster and had problems with it
because of the quorum disk. For unknown reasons storage
had occasional "hiccups" that caused the quorum disks to
be unavailable for short spells, which in turn caused
unnecessary failovers.

I'd recommend a three node cluster.

Yours,
Laurenz Albe

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2012-12-03 10:44:01 Re: Setting up High Availability Group of PostgreSQL instances using RedHat Cluster Suite
Previous Message Albe Laurenz 2012-12-03 10:19:17 Re: base backup requirements for PITR