| From: | Matt Miller <mattm(at)epx(dot)com> |
|---|---|
| To: | Carlos Henrique Reimer <carlosreimer(at)yahoo(dot)com(dot)br> |
| Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org, Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
| Subject: | Re: Postgresql replication |
| Date: | 2005-08-25 19:54:49 |
| Message-ID: | 1124999689.3076.8.camel@dbamm01-linux |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > http://pgfoundry.org/projects/pgcluster/ which provides syncronous
> > multi-master clustering.
>
> He specifically said that pgcluster did not work for him
> because ...PGCluster requires that there be a load balancer and a
> replicator centrally located managing the cluster. If a network
> problem happens at the centralized location, it would bring down all
> locations completely.
I think the load balancer is an optional component. Clients can connect
either to a load balancer, or directly to a specific machine.
Also, I think pgcluster can operate async. If the system runs in
"normal" mode then the client gets a response as soon as the transaction
is committed on the local machine. In "reliable" mode the client waits
for the commit to happen on all machines.
See
http://pgcluster.projects.postgresql.org/structure_of_replication.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2005-08-25 20:05:19 | Re: Postgresql replication |
| Previous Message | Carlos Henrique Reimer | 2005-08-25 19:26:57 | Re: Postgresql replication |