pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Partitioning / Clustering
Date: Tue, 10 May 2005 10:46:24 -0700
Message-ID: <200505101046.25108.josh@agliodbs.com> (raw)
In-Reply-To: <DCFAEF09-885E-492C-A885-EEE405E7773F@advfn.com>
References: <5F94B6EB-3925-4CD3-A67F-4310890B438A@advfn.com>
	<4280C801.80603@arbash-meinel.com>
	<DCFAEF09-885E-492C-A885-EEE405E7773F@advfn.com>

Alex,

> This is why I mention partitioning. It solves this issue by storing  
> different data sets on different machines under the same schema.  

That's clustering, actually.  Partitioning is simply dividing up a table into 
chunks and using the chunks intelligently.   Putting those chunks on seperate 
machines is another thing entirely.  

We're working on partitioning through the Bizgres sub-project:
www.bizgres.org  / http://pgfoundry.org/projects/bizgres/
... and will be pushing it to the main PostgreSQL when we have something.

I invite you to join the mailing list.

> These seperate chunks of the table can then be replicated as well for  
> data redundancy and so on. MySQL are working on these things, 

Don't hold your breath.   MySQL, to judge by their first "clustering" 
implementation, has a *long* way to go before they have anything usable.  In 
fact, at OSCON their engineers were asking Jan Wieck for advice.

If you have $$$ to shell out, my employer (GreenPlum) has a multi-machine 
distributed version of PostgreSQL.  It's proprietary, though.  
www.greenplum.com.

If you have more time than money, I understand that Stanford is working on 
this problem:
http://www-db.stanford.edu/~bawa/

But, overall, some people on this list are very mistaken in thinking it's an 
easy problem.   GP has devoted something like 5 engineers for 3 years to 
develop their system.  Oracle spent over $100 million to develop RAC.  

> but PG   
> just has a bunch of third party extensions, I wonder why these are  
> not being integrated into the main trunk :/ 

Because it represents a host of complex functionality which is not applicable 
to most users?  Because there are 4 types of replication and 3 kinds of 
clusering and not all users want the same kind?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (49+ messages)  latest in thread

Message-ID: <200505101046.25108.josh@agliodbs.com>
Permalink:  ../200505101046.25108.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200505101046.25108.josh@agliodbs.com

 · 

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: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com
  Subject: Re: Partitioning / Clustering
  In-Reply-To: <200505101046.25108.josh@agliodbs.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