public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Simon Riggs <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Replication documentation addition
Date: Tue, 24 Oct 2006 22:54:13 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Simon Riggs wrote:
> On Tue, 2006-10-24 at 00:20 -0400, Bruce Momjian wrote:
> > Here is a new replication documentation section I want to add for 8.2:
> >
> > ftp://momjian.us/pub/postgresql/mypatches/replication
> >
> > Comments welcomed.
>
> It's a very good start to a complete minefield of competing solutions.
>
> My first thought would be to differentiate between clustering and
> replication, which will bring out many differences.
I have gone with "fail-over" and "load balancing" in the updated text.
> My second thought would be to differentiate between load balancing,
> multi-threading, parallel query, high availability and recoverability,
> which would probably sort out the true differences in the above mix. But
> that wouldn't help most people and almost everybody would find fault.
Yep.
> IMHO most people I've spoken to take "replication" to mean an HA
> solution, so perhaps we should cover it in those terms.
Yes, I removed any reference to replication. It seemed too general.
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (117+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Replication documentation addition
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox