public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeff Frost <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Chris Browne <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] Replication documentation addition
Date: Tue, 14 Nov 2006 14:40:03 -0800 (PST)
Message-ID: <Pine.LNX.4.64.0611141434020.23695@discord.home.frostconsultingllc.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Tue, 14 Nov 2006, Bruce Momjian wrote:

>>> We had a long discussion about that and felt that recommending
>>> commercial products or even every open source project was too much.  The
>>> idea was that we should reference a web page that has them all mentioned,
>>> but no one has set one up yet.
>>
>> That makes sense, I just hate to see us say something like "Oracle can do
>> this with RAC but PostgreSQL cannot."
>
> Agreed.  I think we would mention any PostgreSQL solution for this, even
> if it is not open source.  We mention solutions as examples in this part
> of the documentation.
>
> FYI, as far as I know, Continuent's solution is "Query Broadcast Load
> Balancing", not clustering.

I would speculate that your terminology is slightly more accurate than mine. 
The do query broadcast, but they also do a bit more with it than that as they 
evaluate many of the non deterministic write queries on a particular server 
and update the broadcast query so each db gets the same value.

I guess middleware of this sort automatically ends up in the query broadcast 
category.  It just sounds awfully similar to the description of cluster for 
load balancing:

In clustering, each server can accept write requests, and these write requests 
are broadcast from the original server to all other servers before each 
transaction commits.

I guess it's kind of a fine line how it gets defined?

-- 
Jeff Frost, Owner 	<[email protected]>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954

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: [HACKERS] Replication documentation addition
  In-Reply-To: <Pine.LNX.4.64.0611141434020.23695@discord.home.frostconsultingllc.com>

* 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