Re: High Avaliable in the PostgreSQL. - Mailing list pgsql-admin

From adey
Subject Re: High Avaliable in the PostgreSQL.
Date
Msg-id 1c66bda80705302230p7ed40acam8f39e3fea2a00ac6@mail.gmail.com
Whole thread Raw
In response to High Avaliable in the PostgreSQL.  (Fernando Ike de Oliveira <fike@midstorm.org>)
Responses Re: High Avaliable in the PostgreSQL.  (Andrew Sullivan <ajs@crankycanuck.ca>)
List 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@midstorm.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

pgsql-admin by date:

Previous
From: Jon Colverson
Date:
Subject: Re: Attempt to re-archive existing WAL logs after restoring from backup
Next
From: Kristo Kaiv
Date:
Subject: Re: High Avaliable in the PostgreSQL.