Re: Cluster/Replication - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: Cluster/Replication
Date
Msg-id dcc563d10710191130i6f1fbea3n9f09ac46b977e9b6@mail.gmail.com
Whole thread Raw
In response to Re: Cluster/Replication  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-admin
On 10/19/07, Joshua D. Drake <jd@commandprompt.com> wrote:
> On Fri, 19 Oct 2007 12:43:40 -0400
> Sean Brown <sbrown@eaglepress.com> wrote:
>
> > I believe this has come up before, and I am still researching how to
> > do this and figured asking was probably a good idea as hopefully I
> > can either get some direction or someone can point me at something I
> > haven't seen yet.
>
> Why do you have a synchronous requirement?

He said something about losing any data due to the loss of the master
being unacceptable, so synchronous was the only way to go.

But if the machines are separated by any real distance, the speed /
latency of the link will be the deciding factor in the write
performance of the whole system.

I think they might be better off having a local synchronous clustering
solution (i.e. two machines running in failover on shared storage or
something) and then async rep cross country if there's any distance to
the other server.  What to do about slony not handling LOBs I don't
know.

pgsql-admin by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Trigger AFTER UPDATE OR INSERT
Next
From: "Scott Marlowe"
Date:
Subject: Re: Cluster/Replication