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

Re: High Avaliable in the PostgreSQL.

From: adey <adey11(at)gmail(dot)com>
To: "Fernando Ike de Oliveira" <fike(at)midstorm(dot)org>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: High Avaliable in the PostgreSQL.
Date: 2007-05-31 05:30:20
Message-ID: 1c66bda80705302230p7ed40acam8f39e3fea2a00ac6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
HP was providing CA (Continuous Access) software that was claimed to provide
WAN SAN replication by repeating IO in exactly the sequence it was generated
on the master, to the slave. SO while there was a delay, updates on the
slave would be sequentially intact, providing a good level of integrity for
database rollback on the slave in the event of recovery on the slave / DR
system. I'm not sure this would be sufficient for 99.9% uptime though, as
there would be some startup requirements on the slave.

On 5/31/07, Fernando Ike de Oliveira <fike(at)midstorm(dot)org> wrote:
>
> Hi,
>
>
>        I need solution to PostgreSQL for High Available, originally
> was 99,7% but considering the current necessities, change percentual
> to 99,99%. I think in solution probability  pgpool-2 or Heartbeat +
> GFS. The PostgreSQL servers will be in different physical places.
>
>        Suggestions?
>
>
>
> Kind Regards,
> --
> Fernando Ike
> http://www.midstorm.org/~fike/weblog
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>

In response to

Responses

pgsql-admin by date

Next:From: Kristo KaivDate: 2007-05-31 06:45:06
Subject: Re: High Avaliable in the PostgreSQL.
Previous:From: Jon ColversonDate: 2007-05-31 04:58:26
Subject: Re: Attempt to re-archive existing WAL logs after restoring from backup

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