From: Hervé Piedvache <herve@elma.fr>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Thu, 20 Jan 2005 15:36:08 +0100
Message-ID: <200501201536.08656.herve@elma.fr> (raw)
In-Reply-To: <41EFBF05.6000509@familyhealth.com.au>
References: <200501201503.31241.herve@elma.fr>
<41EFBF05.6000509@familyhealth.com.au>
Le Jeudi 20 Janvier 2005 15:24, Christopher Kings-Lynne a écrit :
> > Is there any solution with PostgreSQL matching these needs ... ?
>
> You want: http://www.slony.info/
>
> > Do we have to backport our development to MySQL for this kind of problem
> > ? Is there any other solution than a Cluster for our problem ?
>
> Well, Slony does replication which is basically what you want :)
>
> Only master->slave though, so you will need to have all inserts go via
> the master server, but selects can come off any server.
Sorry but I don't agree with this ... Slony is a replication solution ... I
don't need replication ... what will I do when my database will grow up to 50
Gb ... I'll need more than 50 Gb of RAM on each server ???
This solution is not very realistic for me ...
I need a Cluster solution not a replication one or explain me in details how I
will do for managing the scalabilty of my database ...
regards,
--
Hervé
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: herve@elma.fr, chriskl@familyhealth.com.au
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <200501201536.08656.herve@elma.fr>
* 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