| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manoj Govindassamy | 2012-01-18 01:54:04 | Re: PG synchronous replication and unresponsive slave |
| Previous Message | Kevin Grittner | 2012-01-17 23:09:11 | Re: apt installation postgresql 8.3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondrej Ivanič | 2012-01-18 01:20:47 | Re: self referencing table. |
| Previous Message | David Johnston | 2012-01-18 01:01:07 | Re: self referencing table. |