From: RW <postgres@tauceti.net>
To: pgsql-admin@postgresql.org
Subject: Re: Pg/CyberCluster test results
Date: Fri, 22 Aug 2008 16:06:15 +0200
Message-ID: <48AEC7D7.4020501@tauceti.net> (raw)
In-Reply-To: <48AEC4A7.6050508@tauceti.net>
References: <767392.31997.qm@web37902.mail.mud.yahoo.com>
<48AEC4A7.6050508@tauceti.net>
Maybe some people haven't read this site here:
http://www.postgresqldocs.org/wiki/Replication,_Clustering,_and_Connection_Pooling
It gives a nice overview. Another interesting project which isn't
production ready yet is Postgres-R (http://www.postgres-r.org/)
Robert
RW wrote:
> I hoped that it would be easier to get the nodes back in sync
> but it seems that all Postgres Multi-Master solutions are not
> reliable at the moment. I've planed to test CyberCluster
> this weekend but I already suspected that this rsync solutions
> have some shortcomings. Sniff...
>
> It seems that we have to wait for PGCluster-II which isn't a
> "shared nothing" solution. Instead all files are on a shared
> medium like SAN or iSCSI and all instances uses this medium
> (similar to Oracle).
>
> Robert
>
> CG wrote:
>> I've been testing Cybercluster (which is a modified PgCluster) ... I
>> have two back-end databases, one load balancer, and one replicator.
>> I've been testing failover and rebuilding a degraded cluster, and I'm
>> finidng that it is REALLY easy for the two back-ends to get out of
>> sync with each other. This is very disturbing. I was wondering if
>> anyone has experience with solving this problem.
>>
>>
>>
>>
>
>
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: postgres@tauceti.net
Subject: Re: Pg/CyberCluster test results
In-Reply-To: <48AEC7D7.4020501@tauceti.net>
* 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