From: Markus Schiltknecht <markus@bluegap.ch>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication
Date: Thu, 21 Jun 2007 17:14:39 +0200
Message-ID: <467A95DF.50307@bluegap.ch> (raw)
In-Reply-To: <20070620150646.GP31426@phlogiston.dyndns.org>
References: <4671CBBA.6010104@emolecules.com>
<4671CDB1.3090708@commandprompt.com>
<4676C3A9.7070703@bluegap.ch>
<4676CFCB.5070505@emolecules.com>
<4676D4F6.1020508@bluegap.ch>
<20070620150646.GP31426@phlogiston.dyndns.org>
Hi,
Andrew Sullivan wrote:
> This isn't quite true. Slony-II was originally conceived by Jan as
> an attempt to implement some of the Postgres-R ideas.
Oh, right, thanks for that correction.
> Part of the problem, as near as I could tell, was that we had no
> group communication protocol that would really work. Spread needed a
> _lot_ of work (where "lot of work" may mean "rewrite"), and I just
> didn't have the humans to put on that problem. Another part of the
> problem was that, for high-contention workloads like the ones we
> happened to be working on, an optimistic approach like Postgres-R is
> probably always going to be a loser.
Hm.. for high-contention on single rows, sure, yes - you would mostly
get rollbacks for conflicting transactions. But the optimism there is
justified, as I think most real world transactions don't conflict (or
else you can work around such high single row contention).
You are right in that the serialization of the GCS can be bottleneck.
However, there's lots of research going on in that area and I'm
convinced that Postgres-R has it's value.
Regards
Markus
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-performance@postgresql.org
Cc: markus@bluegap.ch, ajs@crankycanuck.ca
Subject: Re: Replication
In-Reply-To: <467A95DF.50307@bluegap.ch>
* 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