|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Markus Schiltknecht <markus(at)bluegap(dot)ch>|
|Cc:||Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-docs(at)postgresql(dot)org|
|Views:||Raw Message | Whole Thread | Download mbox|
Markus Schiltknecht wrote:
> I wrote:
> > That reminds me of the requirement of having Multi Master Replication in
> > place to do Parallel Query Execution. Sync Multi Master Replication
> > being better, while Async Multi Master Replication obviously leads to
> > inconsistent responses, when queried in parallel. That may be acceptable
> > in certain situations.
> Oops, during rereading "Clustering For Parallel Query Execution", I've
> noticed that you mention Data Partitioning as one possible way to do
> Parallel Query Execution. Thus Multi Master Replication obviously is not
> a requirement, but just another way to allow for Parallel Query
> Execution. Mentioning that as well would probably be good.
Uh, multi-master replication allows for load balancing, but it doesn't
help a single query to run any faster. Think of having only one query
running on the cluster. Parallel execution allows a single query to use
more than one computer, right?
> IMHO, the advice to use multiple, independent databases to do parallel
> query execution sounds a little meager. Of course it's also parallel
> query execution, but it's not what most people suspect to find under
> that section, I would guess.
Uh, this confuses me. What is missing? You split tables across
Bruce Momjian bruce(at)momjian(dot)us
+ If your life is a hard drive, Christ can be your backup. +
|Next Message||Bruce Momjian||2006-11-22 04:28:43||Re: [Pgcluster-general] PostgreSQL Documentation of|
|Previous Message||Bruce Momjian||2006-11-22 04:00:06||Re: "Clustering"|