From: | "Alexander Staubo" <alex(at)purefiction(dot)net> |
---|---|
To: | "mljv(at)planwerk6(dot)de" <mljv(at)planwerk6(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org, "Markus Schiltknecht" <markus(at)bluegap(dot)ch>, "David Fetter" <david(at)fetter(dot)org> |
Subject: | Re: pgpool2 vs sequoia |
Date: | 2007-08-06 18:05:39 |
Message-ID: | 88daf38c0708061105n3ee0bf9dl712f261aa3fe4d27@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/6/07, mljv(at)planwerk6(dot)de <mljv(at)planwerk6(dot)de> wrote:
> the last few years we ran with horizontal partitioning. i always ran into
> problems with horizontal partioning because few tables must be shared across
> the databases and sometimes things are moving and i got lot of trouble with
> my primary keys being the same on different nodes.
Note that pgpool2 can be used to implement transparent horizontal
partitioning. Have you looked at it?
> At the moment i see the following solutions:
> 1 synchronous replication: pgpool2 (or sequoia)
> 2 horizontal partitioning
> 3 better hardware
> 4 asynchronous replication: slony
For #1 there's also PGCluster (which, incidentally, is not the same as
PGCluster-II, a shared-disk solution), which does synchronous
multimaster replication.
The project has historically looked a bit dead, but they just released
a new version and moved to a Trac-based web site at
http://www.pgcluster.org/.
One major downside to PGCluster is that it uses a modified version of
PostgreSQL, and it usually lags a few releases behind.
Alexander.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2007-08-06 18:09:32 | Re: new line in psotgres |
Previous Message | Michael Glaesemann | 2007-08-06 17:40:23 | Re: pg_dump of only the structure from a client such as ruby |