public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim C. Nasby <[email protected]>
To: Markus Schiltknecht <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Hannu Krosing <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: [HACKERS] Replication documentation addition
Date: Wed, 25 Oct 2006 08:57:41 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Wed, Oct 25, 2006 at 11:38:11AM +0200, Markus Schiltknecht wrote:
> I can't really get excited about the exclusion of the term 
> 'replication', because it's what most people are looking for. It's a 
> well known term. Sorry if it sounded that way, but I've not meant to 
> avoid that term.
<snip> 
> IMHO, it does not make sense to speak of a synchronous replication for a 
> 'Shared Disk Fail Over'. It's not replication, because there's no replica.

Those to statements are at odds with each other, at least based on
everyone I've ever talked to in a commercial setting. People will use
terms like 'replication', 'HA' or 'clustering' fairly interchangably.
Usually what these folks want is some kind of high-availability
solution. A few are more concerned with scalability. Sometimes it's a
combination of both. That's why I think it's good for the chapter to
deal with both aspects of this.
-- 
Jim Nasby                                            [email protected]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

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], [email protected], [email protected]
  Subject: Re: [HACKERS] 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