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

Re: Replication/Failover/HA solution

From: Andrew Biagioni <andrew(dot)biagioni(at)e-greek(dot)net>
To: pgsql-admin(at)postgresql(dot)org,Andrew Sullivan <andrew(at)libertyrms(dot)info>
Subject: Re: Replication/Failover/HA solution
Date: 2003-07-22 21:25:28
Message-ID: JGHCJG5YGFML54YSGAOKF5NIVU94HG.3f1dabc8@Laptop (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
7/22/03 3:32:03 PM, Andrew Sullivan <andrew(at)libertyrms(dot)info> wrote:

>On Mon, Jul 21, 2003 at 06:11:15PM -0400, Renney Thomas wrote:
>> I am having a hard time selecting a Replication/Failover/HA solution for 
>> PGSQL. What is troubling is the number of solutions available in various 
>> states of development.  Does the fact that dbmirror and rserv appear in 
>> the contrib directory, mean that they should be looked upon with more 
>> legitimacy? Any suggestions?
>Some code that descended from rserv is about to be released to the
>community.  We use it today in production.  It's pretty rough around
>the edges, and it depends on Java, if you can stand that, but it's
>definitely battle-tested.

Sorry -- by "production", what release version do you mean?



>Andrew Sullivan                         204-4141 Yonge Street
>Liberty RMS                           Toronto, Ontario Canada
><andrew(at)libertyrms(dot)info>                              M2P 2A8
>                                         +1 416 646 3304 x110
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>      message can get through to the mailing list cleanly

In response to


pgsql-admin by date

Next:From: Srinivas KotapallyDate: 2003-07-22 21:47:34
Subject: Using the /var/lib/pgsql/data directory in the absense of a backup for recovery
Previous:From: Ian BarwickDate: 2003-07-22 21:18:58
Subject: Re: How can I set a default schema for a session

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