From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication |
Date: | 2009-06-26 20:14:56 |
Message-ID: | 80202B71-6FFA-43E7-97DA-8C262B88F495@hi-media.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Le 25 juin 09 à 11:26, Jasen Betts a écrit :
> On 2009-06-23, Mike Christensen <mike(at)kitchenpc(dot)com> wrote:
>
>> Does anyone actually have that (any node
>> can go down and the others still replicate amongst themselves?)
>
> you are describing usenet. (it was not designed for relational
> database
> replication but it does have that feature)
http://postgres-r.org/about/about
Reliability, Availability and Scalability
Mirroring the data on multiple nodes enhances reliability of the
database system. As Postgres-R is using a group communication system
it is easily possible to add or remove nodes on the running system.
Crashing nodes are automatically detected and removed, thus do not
affect the operating of the database system. This facilitates
administration tasks and ensures greater availability and scalability
of the database system.
Regards,
--
dim
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Troutwine | 2009-06-26 20:35:00 | Re: Terrible Write Performance of a Stored Procedure |
Previous Message | Dimitri Fontaine | 2009-06-26 20:10:09 | Re: masking the code |