What is a good way to horizontal shard in postgresql?

PostgreSQL allows partitioning in two different ways. One is by range and the other is by list. Both use table inheritance to do partition Partitioning by range, usually a date range, is the most common, but partitioning by list can be useful if the variables that is the partition are static and not skewed Partitioning is done with table inheritance so the first thing to do is set up new child tables CREATE TABLE measurement ( x int not null, y date not null, z int ); CREATE TABLE measurement_y2006 ( CHECK ( logdate >= DATE '2006-01-01' AND logdate = DATE '2007-01-01' AND logdate = DATE '2006-01-01' AND NEW.

Logdate = DATE '2007-01-01' AND NEW. Logdate '; END IF; RETURN NULL; END; $$ LANGUAGE plpgsql These examples are simplified versions of the postgresql documentation for easier reading I am not familiar with pgpool2, but gridsql is a commercial product designed for EnterpriseDB, a commercial database that is built on top of postgresql. Their products are very good, but I do not think that it will work on standard postgresl.

PostgreSQL allows partitioning in two different ways. One is by range and the other is by list. Both use table inheritance to do partition.

Partitioning by range, usually a date range, is the most common, but partitioning by list can be useful if the variables that is the partition are static and not skewed. Partitioning is done with table inheritance so the first thing to do is set up new child tables. CREATE TABLE measurement ( x int not null, y date not null, z int ); CREATE TABLE measurement_y2006 ( CHECK ( logdate >= DATE '2006-01-01' AND logdate = DATE '2007-01-01' AND logdate = DATE '2006-01-01' AND NEW.

Logdate = DATE '2007-01-01' AND NEW. Logdate '; END IF; RETURN NULL; END; $$ LANGUAGE plpgsql; These examples are simplified versions of the postgresql documentation for easier reading. I am not familiar with pgpool2, but gridsql is a commercial product designed for EnterpriseDB, a commercial database that is built on top of postgresql.

Their products are very good, but I do not think that it will work on standard postgresl.

Very thorough. +1. – j_random_hacker Jan 20 '10 at 0:30 GridSQL is GPL and it does work upon standard postgres.

– David Mar 15 '10 at 16:30.

Pl/proxy (by Skype) is a good solution for this. It requires your access to be through a function API, but once you have that it can make it pretty transparent.

Well, if the question is about sharding, then pgpool and postgresql partitioning features are not valid answers. Partitioning assumes the partitions are on the same server. Sharding is more general and is usually used when the database is split on several servers.

Sharding is used when Partitioning is not possible any more, e. G for large database that cannot fit on a single disk. For true sharding then Skype's pl/proxy is probably the best.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.