pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jnasby@pervasive.com>
To: Louis Gonzales <louis.gonzales@linuxlouis.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgresql-R
Date: Wed, 8 Mar 2006 15:48:43 -0600
Message-ID: <D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com> (raw)
In-Reply-To: <440DF3FF.9060001@linuxlouis.net>
References: <440DED31.1060704@linuxlouis.net>
	<20060307203530.GG58405@pervasive.com>
	<440DF3FF.9060001@linuxlouis.net>

On Mar 7, 2006, at 2:58 PM, Louis Gonzales wrote:

> Based on:
> Postgres based Replication Projects
>
> PG Replication
> Postgres-R: Dr. Kemme's Site, Paper, Publications, Replication  
> Work, The Horus Project and Emsemble
> DRAGON: Database Replication based on Group Communication
> The Slony-1 Project
> PGCluster
> DBBalancer
> PostgreSQL Replicator: Tutorial, Paper, Techdocs
> eRServer: Techdocs
> DBMirror: Will be in the 7.3 contrib directory.
> Usogres: Techdocs
> From:  http://gborg.postgresql.org/project/pgreplication/ 
> genpage.php?replication_research
> I was under the impression that "Postgres-R" - I misspelled it as  
> "postgresql-R" - is a database clustering software.  I downloaded  
> the sources for this and it's supposed to work with "spread."  I  
> apologize if I'm mistaken?

Well, AfAIK it's quasi-clustering. I'd describe it as a mix between  
sync and async multi-master replication. Its concepts are the basis  
behind Slony-II AFAIK.

> I will certainly take a look into Slony-1, as you suggest.  Did you  
> have any good links to this?  Have you gone through an install on  
> Solaris 9 w/Postgresl v8.0?
>
> WAN != LAN, where my database server is not in the same city as the  
> target system to cluster with; for my worse case scenario, could be  
> from east coast to west coast.

The issues you'll run into are that in a high-load scenario, the  
latency on that link could become a real issue, as could bandwidth  
(actually, bandwidth is probably the bigger issue). The other  
downside is that slony is decidedly async; if you have to fail over  
you're probably going to lose some recently committed data. As long  
as that's not an issue then it's your best bet. If it is an issue,  
you'll probably be stuck rolling your own solution using something  
like 2PC.

You should hop on the slony mailing list if you have any questions  
about it.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461





view thread (9+ messages)  latest in thread

Message-ID: <D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com>
Permalink:  ../D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com/
Also on:    postgresql.org/message-id/D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, louis.gonzales@linuxlouis.net
  Subject: Re: postgresql-R
  In-Reply-To: <D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com>
  References: <440DED31.1060704@linuxlouis.net> <20060307203530.GG58405@pervasive.com> <440DF3FF.9060001@linuxlouis.net> <D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox