Skip site navigation (1) Skip section navigation (2)

RE: Partitioning / Clustering

From: <tdrayton(at)extendb(dot)com>
To: <alexs(at)advfn(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: RE: Partitioning / Clustering
Date: 2005-05-10 18:26:02
Message-ID: 0MKyxe-1DVZSc2SM6-0007Nl@mrelay.perfora.net (view raw or flat)
Thread:
Lists: pgsql-performance
Hi Alex,

Actually, our product can partition data among several clustered nodes
running PostgreSQL, if that is what you are looking for. Data is
distributed based on a designated column. Other tables can be
replicated to all nodes.

For SELECTs, it also knows when it can join locally or it needs to ship
rows as part of the query plan. For FK constraints (discussed here), it
also knows when it can enforce them locally or not.

Please let me know if you would like some more information.

Regards,

Tom Drayton
ExtenDB
http://www.extendb.com



> This is why I mention partitioning. It solves this issue by storing  
> different data sets on different machines under the same schema.  
> These seperate chunks of the table can then be replicated as 
> well for  
> data redundancy and so on. MySQL are working on these things, but PG  
> just has a bunch of third party extensions, I wonder why these are  
> not being integrated into the main trunk :/ Thanks for 
> pointing me to  
> PGCluster though. It looks like it should be better than 
> Slony at least.
>

pgsql-performance by date

Next:From: Matt OlsonDate: 2005-05-10 18:36:31
Subject: Re: Prefetch
Previous:From: Greg StarkDate: 2005-05-10 18:13:11
Subject: Re: Prefetch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group