From: Markus Schiltknecht <markus@bluegap.ch>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: High Availability, Load Balancing, and Replication Feature Matrix
Date: Fri, 23 Nov 2007 14:21:22 +0100
Message-ID: <4746D3D2.2080809@bluegap.ch> (raw)
In-Reply-To: <200711192121.lAJLLAi07431@momjian.us>
References: <200711192121.lAJLLAi07431@momjian.us>
Hello Bruce,
Bruce Momjian wrote:
> Uh, to me the issue is something like pgpool and Sequoia, where the
> _master_/replication is happening _outside_ the server
Well, you are saying that the controllers are the masters and do
replication. I can see the reasoning behind it: they are the only nodes
which allow write access, seen from the outside.
However, I don't consider these controllers to be masters nor slaves,
because they don't carry a replica of the data. Instead I'm considering
the database nodes which are (synchronously or not) processing the
writing transactions on behalf of the controller to be the masters. They
do all the work and the locking, and they carry the replicated data.
PgCluster (and therefore Cybercluster, too) seem to follow my
definition, as they are advertising themselves as multi-master
replication solutions (even though they only support one single
controller, AFAICT).
I didn't find any self-definition of PgPool's replication feature nor
Sequoias. However, I'd argue that both are generally considered
synchronous multi-master replication solutions as well, even if there's
only one controller.
> vs something
> like Oracle RAC where it is happening inside the server.
..or like Postgres-R :-)
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-docs@postgresql.org
Cc: markus@bluegap.ch, bruce@momjian.us
Subject: Re: High Availability, Load Balancing, and Replication Feature Matrix
In-Reply-To: <4746D3D2.2080809@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