Re: Database replication... - Mission Critical DBMS's -- - Mailing list pgsql-general

From Robert Treat
Subject Re: Database replication... - Mission Critical DBMS's --
Date
Msg-id 1035991127.15257.36.camel@camel
Whole thread Raw
In response to Re: Database replication... - Mission Critical DBMS's --  (Bill Gribble <grib@linuxdevel.com>)
Responses Re: Database replication... - Mission Critical DBMS's --  (Andrew Sullivan <andrew@libertyrms.info>)
List pgsql-general
You might want to check out
http://gborg.postgresql.org/genpage?replication_research which has
information and links to several replication solutions for postgresql.

the techdocs.postgresql.org website also has a good number of papers
regarding replication, as well as a "high availability how-to" that
would probably be worth reading.

Robert Treat

On Wed, 2002-10-30 at 09:24, Bill Gribble wrote:
> On Tue, 2002-10-29 at 17:56, Greg Patnude wrote:
> > Does anyone know of a reasonable means of synchronizing two (or more)
> > postgreSQL database servers in order to maintain two COMPLETE concurrent
> > copies of the same database ?
>
> I'm not sure how complete it is (just starting to look at this myself)
> but 'dbbalancer' at least makes some claims to this.  It acts as
> (basically) a postgresql proxy server, and can send queries to multiple
> servers.  My presumption would be that if you initialize 2 databases to
> a known identical start, have all the same triggers and rules on both,
> then send all queries to both databases, you will have 2 identical
> databases at the end.
>
> Don't know how well that will work in practice tho.  I should know more
> in the next couple of weeks.
>
> b.g.
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org




pgsql-general by date:

Previous
From: "Johnson, Shaunn"
Date:
Subject: how to terminate a process when kill fails
Next
From: Andrew Sullivan
Date:
Subject: Re: what selects