From: | Gerry Reno <greno(at)verizon(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication |
Date: | 2009-06-26 21:47:59 |
Message-ID: | 4A45420F.3090602@verizon.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dimitri Fontaine wrote:
> 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
I think some disclosure is in order about postgres-r:
"Please note that this is *experimental* software. primarily released
for review by developers familiar with Postgres."
Looks interesting though...
Regards,
Gerry
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-06-26 22:34:20 | Re: Terrible Write Performance of a Stored Procedure |
Previous Message | Scott Marlowe | 2009-06-26 21:32:35 | Re: masking the code |