Skip site navigation (1) Skip section navigation (2)

Re: PG synchronous replication and unresponsive slave

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Manoj Govindassamy <manoj(at)nimblestorage(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: PG synchronous replication and unresponsive slave
Date: 2012-01-18 01:04:47
Message-ID: CAHGQGwFNLAQOT7Rfz2z=bSjgf4S5hFj0xx7F1jP0XnCjVmM3GQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
On Wed, Jan 18, 2012 at 6:37 AM, Manoj Govindassamy
<manoj(at)nimblestorage(dot)com> wrote:
> (2) We are not comfortable moving to PGPool just for automatic failback mode
> on hot-standby failure.

Hmm.. my reply might be misleading. What I meant was to use pgpool-II
as a clusterware for PostgreSQL built-in replication, not as a replication
itself. You can health-check, do failover if necessary and manage the
PostgreSQL replication by using pgpool-II. AFAIK pgpool-II has such an
operation mode. But you are still not comfortable in using pgpool-II in
that way?

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

pgsql-admin by date

Next:From: Manoj GovindassamyDate: 2012-01-18 01:54:04
Subject: Re: PG synchronous replication and unresponsive slave
Previous:From: Kevin GrittnerDate: 2012-01-17 23:09:11
Subject: Re: apt installation postgresql 8.3

pgsql-general by date

Next:From: Ondrej IvaničDate: 2012-01-18 01:20:47
Subject: Re: self referencing table.
Previous:From: David JohnstonDate: 2012-01-18 01:01:07
Subject: Re: self referencing table.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group