From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Joe Tomcat <tomcat(at)mobile(dot)mp>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 7.4? |
Date: | 2003-02-26 21:41:10 |
Message-ID: | 200302261441.10409.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday February 26 2003 8:08, Tom Lane wrote:
> > I would've assumed an asyncronous solution would be far more
> > applicable for
>
> You're just showing bias in the other direction ;-).
Mea culpa.
> Back when I was working for Great Bridge and got to spend a fair
> amount of time at trade shows talking to potential customers, the
> thing we heard over and over again was that people wanted multiple
> servers for reliability/redundancy. That goal seems to me to be
> best served by a symmetric multi-master configuration, which is
> difficult if not impossible to do with async replication.
I also share the objectives of reliability/redundancy. My concern
with syncronous solutions in general is recoverability when one of
two masters fails. Admittedly at the price of intervals of data
inconsistency between master and slave, async solutions can just pop
back online and "catch-up", thus the appeal. In reading a little
more on PG-R, I understand the use of the Spread GCS would seem to
address that recoverability concern along with performance concerns.
Is that your understanding?
As an aside, ERserver looks credible, though the $10,000 pricetag and
closed source are somewhat of a barrier, so I hope an increasingly
useful open-source async solution can further emerge.
Ed
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Bartley | 2003-02-26 21:51:04 | Re: WITHOUT OIDS |
Previous Message | Andrew Bartley | 2003-02-26 21:39:49 | Re: WITHOUT OIDS |