| From: | Hervé Piedvache <herve(at)elma(dot)fr> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL clustering VS MySQL clustering |
| Date: | 2005-01-20 14:36:08 |
| Message-ID: | 200501201536.08656.herve@elma.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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é
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-01-20 14:38:34 | Re: PostgreSQL clustering VS MySQL clustering |
| Previous Message | Stephen Frost | 2005-01-20 14:30:45 | Re: PostgreSQL clustering VS MySQL clustering |