Clustering Database Servers

Slony is the master-slave (not multi-master IIRC) replication environment.

I haven't used it, but apparently there are cognoscenti among us who have.

I would think, a bit, about what kind of "load" (e.g. CPU, network, disk
queues, disk allocation, et cetera) you want to balance before picking up
the hammer .... (sorry to preach...)

hth,

Ross

-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Craig Bryden
Sent: Monday, May 09, 2005 2:42 PM
To: pgsql
Subject: [GENERAL] Clustering Database Servers

Hi

In MS SQL there is a concept of Clustering database servers. This allows for load balancing. Does PostgreSQL have a similar concept?

Thanks
Craig

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Mon, 2005-05-09 at 13:41, Craig Bryden wrote:

Hi

In MS SQL there is a concept of Clustering database servers. This allows for
load balancing.
Does PostgreSQL have a similar concept?

This really kinda depends on what you are tring to load balance. I/O,
parallel users, CPU intensive apps, etc...

Using pgpool and / or slony you can get the same basic effect.

Note that no clustering solution can improve both read and write speed
at the same time while ensuring referential integrity.

There are a few other methods for doing this, take a look through the
pgsql mailing list archives and google for other possible solutions.

As there is no single problem requiring clustering, there is no single
clustering solution that will answer all these problems.