public inbox for [email protected]  

help / color / mirror / Atom feed

From: Markus Schiltknecht <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Jim Nasby <[email protected]>
Cc: Jeff Frost <[email protected]>
Cc: Chris Browne <[email protected]>
Subject: Re: [HACKERS] Replication documentation addition
Date: Mon, 20 Nov 2006 16:35:25 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Good morning Bruce,

Bruce Momjian wrote:
>> Oops, I see Markus Schiltknech likes the term "statement-based
>> replication" better too.  Certainly master-slave communication using
>> "statement-based replication" has the same drawbacks as the broadcast
>> method, but I wanted to highlight that the broadcast was happening
>> outside the server.  Do we need a master/slave "statement-based
>> replication" item and a middleware broadcast item?

Ah, I see you had a much narrower definition of statement-based 
replication in mind. As I've pointed out, there are different 
implementations of 'statement-based replication'. I don't know about 
sequoia, but Postgres-R fails back to statement based replication in 
certain situations. Thus having an external 'program intercept every SQL 
query' is absolutely no necessity of this algorithm, it can very well be 
done inside the db backend, where you can better catch non-deterministic 
functions... but again, that's an implementation detail.

So, do you want to describe pgpool here or do you want to give a more 
general description?

>  <varlistentry>
>   <term>Statement-Based Replication</term>
>   <listitem>
> 
>    <para>
>     In statement-based replication, a program intercepts every SQL
>     query and sends it to all servers.  Each server operates
>     independently.  Read-only queries can be sent to a single server
>     because there is no need for all servers to process it.
>    </para>

If you want to go for the general description, I think the 'each server 
operates independently' is somewhere between confusing and false. And 
again, the last sentence applies to all multi-master replication solutions.

Regards

Markus

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], [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