public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Jeff Frost <[email protected]>
Cc: Chris Browne <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] Replication documentation addition
Date: Tue, 14 Nov 2006 19:11:39 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <Pine.LNX.4.64.0611141534330.23695@discord.home.frostconsultingllc.com>

Jeff Frost wrote:
> On Tue, 14 Nov 2006, Bruce Momjian wrote:
> 
> >> My thinking on the definition of clustering was that there is some smarts for
> >> graceful failover and automated or semi-automated ways of bringing failed DB
> >> servers back up to date and online with the rest of the servers in the
> >> cluster.  All servers need to be able to accept writes, but do we
> >
> > No, even replication servers can have that.
> >
> >> differentiate on where the writes originated (i.e. middleware or another
> >> postgresql server) or on functionality?
> >
> > Fundamentally, broadcast means the queries are being propogated outside
> > the server, with the benefits and limitations inherent in that.
> 
> I'd definitely have to agree with you on that.  I guess I'm trying to decide 
> what differentiates clustering for load balancing from query broadcast based 
> on your text.  Maybe just don't use the word broadcast here:
> 
> "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."
> 
> Unfortunately, I can't seem to come up with anything more clever.

Basically, when you are broadcasting outside the server, you are
broadcasting SQL queries, and those queries do not have information
about non-deterministic functions and have issues with universal commits
on all node.

I think I now see your point about using the word "broadcast" for both
clustering and middle-ware broadcast.  Let me find some new wording and
repost.

-- 
  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: [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