From: Neil Conway <neilc@samurai.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Partitioning / Clustering
Date: Wed, 11 May 2005 14:39:22 +1000
Message-ID: <42818C7A.7020207@samurai.com> (raw)
In-Reply-To: <428177E5.4030704@commandprompt.com>
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
<4280C801.80603@arbash-meinel.com>
<DCFAEF09-885E-492C-A885-EEE405E7773F@advfn.com>
<200505101046.25108.josh@agliodbs.com>
<428172A2.9030503@samurai.com>
<428177E5.4030704@commandprompt.com>
Joshua D. Drake wrote:
> Neil Conway wrote:
>> Oh? What's wrong with MySQL's clustering implementation?
>
> Ram only tables :)
Sure, but that hardly makes it not "usable". Considering the price of
RAM these days, having enough RAM to hold the database (distributed over
the entire cluster) is perfectly acceptable for quite a few people.
(Another deficiency is in 4.0, predicates in queries would not be pushed
down to storage nodes -- so you had to stream the *entire* table over
the network, and then apply the WHERE clause at the frontend query node.
That is fixed in 5.0, though.)
-Neil
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: pgsql-performance@postgresql.org
Cc: neilc@samurai.com, jd@commandprompt.com, josh@agliodbs.com
Subject: Re: Partitioning / Clustering
In-Reply-To: <42818C7A.7020207@samurai.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox