X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C01993A4529 for ; Thu, 20 Jan 2005 14:36:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07540-04 for ; Thu, 20 Jan 2005 14:36:05 +0000 (GMT) Received: from mailer.elma.loc (mail.elma.fr [213.41.14.138]) by svr1.postgresql.org (Postfix) with ESMTP id 95E553A44BE for ; Thu, 20 Jan 2005 14:36:07 +0000 (GMT) Received: from mailer.elma.loc (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 964ADEC206; Thu, 20 Jan 2005 15:36:53 +0100 (CET) Received: from herve.elma.fr (herve.elma.fr [10.0.1.2]) by mailer.elma.loc (Postfix) with ESMTP id 7096FEC07F; Thu, 20 Jan 2005 15:36:53 +0100 (CET) From: =?iso-8859-15?q?Herv=E9_Piedvache?= Organization: Elma =?iso-8859-15?q?Ing=E9nierie?= Informatique To: Christopher Kings-Lynne Subject: Re: PostgreSQL clustering VS MySQL clustering Date: Thu, 20 Jan 2005 15:36:08 +0100 User-Agent: KMail/1.7.1 Cc: pgsql-performance@postgresql.org References: <200501201503.31241.herve@elma.fr> <41EFBF05.6000509@familyhealth.com.au> In-Reply-To: <41EFBF05.6000509@familyhealth.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200501201536.08656.herve@elma.fr> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.29 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, INFO_TLD X-Spam-Level: X-Archive-Number: 200501/273 X-Sequence-Number: 9963 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é