X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id EF1D79DCAD7 for ; Fri, 2 Dec 2005 23:32:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72789-05 for ; Fri, 2 Dec 2005 23:32:13 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by postgresql.org (Postfix) with ESMTP id C61A29DD896 for ; Fri, 2 Dec 2005 23:32:15 -0400 (AST) Received: by wproxy.gmail.com with SMTP id 55so836156wri for ; Fri, 02 Dec 2005 19:32:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=rZuD1RxQx4VQ7wksN7gG49QFqx/+MmW5M4Ki8i8KRhh9pAhMrtpHYBulpy+gNe5fHOt95PpVvjnCrM6KMDWu3B2VZ2G4CipBcdAAAlvSD6RR7Jx5dAh8xKRGoDpcpO7lD0Zz7pEyi4X0OOzmVKZtBtUoVKF2iE5giZYtJ4iLVmc= Received: by 10.65.11.4 with SMTP id o4mr1933942qbi; Fri, 02 Dec 2005 19:32:20 -0800 (PST) Received: by 10.64.153.16 with HTTP; Fri, 2 Dec 2005 19:32:20 -0800 (PST) Message-ID: <731083980512021932v7b3236cdg@mail.gmail.com> Date: Sat, 3 Dec 2005 01:32:20 -0200 From: Rodrigo Hjort To: pgsql-admin@postgresql.org Subject: Re: Postgresql Replication High Availability MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.322 required=5 tests=[AWL=0.322] X-Spam-Score: 0.322 X-Spam-Level: X-Archive-Number: 200512/22 X-Sequence-Number: 19742 We're on the same situation. --> PGCluster Actualy, we installed and tested PGCluster on UML (User Mode Linux) environment and real distributed stations. There were a lot of critical issues on it! For example, once a user tries to connect to an unexisting database, the load balancer fails and needs to be restarted... Another: if closed by Ctrl+C, the postmaster starts in an infinite loop! We sent these problems to its User List, and we noted that there are other unsolved issues and a lot of patches not officially posted yet... One thing that made us afraid is that the project isn't updated since march of 2005! http://pgcluster.projects.postgresql.org/ Too much risky to our critical mission database, we thought! --> ClusGres This application should be very promisor, if it weren't "vaporware"... http://www.linuxlabs.com/clusgres.html --> C-JDBC / Sequoia It looks like we're gonna stay with this solution, as I explained on a later e-mail. http://c-jdbc.objectweb.org/ http://sequoia.continuent.org/ ------ Christopher wrote: I am currently looking into high availability solutions for Postgresql. I am designing system that should not have a single point of failure.=20 I would like to at run-time Add new hardware and add them to my (cluster ) environment without shutting anything down. Please advise, Thanks #1. Is PGCluster production environment ready? #2. CJDBC.... has anyone used this in production environment with Postgresq= l? #3. Any other solutions viable for production environments? ------ Regards, Rodrigo Hjort Linux User #348191 (http://counter.li.org)