Bruce Momjian wrote:
> Bruce Momjian wrote:
> > Josh Berkus wrote:
> > > Jim,
> > >
> > > > That's true of simple query broadcasting (ie: pgpool), but not true ?
> > > > of Continuent/Sequoia. Continuent's software adds a lot of additional ?
> > > > features on top of simple query broadcasting, making it far more ?
> > > > robust than simply spewing queries out to every node in the cluster. ?
> > > > You still have to be very careful with how you use it, but not nearly ?
> > > > as much as with simpler solutions.
> > >
> > > I think the general term is "statement-based replication", not "broadcasting".
> >
> > Well, the problem is that you can use a statement-based method to
> > replication from a master to a slave. I think MySQL used to use this
> > method, or still does, so I don't think the term "statement-based" is
> > clear enough, though I am open to other terms than "broadcast".
>
> 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?
OK, new text:
<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>
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
