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 A88129DCBB6 for ; Sun, 4 Dec 2005 14:41:38 -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 40982-10 for ; Sun, 4 Dec 2005 14:41:35 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by postgresql.org (Postfix) with ESMTP id 52BBF9DCB94 for ; Sun, 4 Dec 2005 14:41:35 -0400 (AST) Received: by wproxy.gmail.com with SMTP id i11so467117wra for ; Sun, 04 Dec 2005 10:41:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=K2i6YHzvILK8la1LUeXzxMCaA2R7LYNnQGv2gOr38PkwdREW1fRQfHNIVBGeicUIRp/GH+88Yq+vO3V6ZyGxmhxscF5GO+9qSNQxhpa5X96HQ6SMQzsQzQ6DTYMRh7NZdDHSY02IONWDEM2dOkitzILlV5krmjLIfVSlwZORDv4= Received: by 10.64.193.4 with SMTP id q4mr2328592qbf; Sun, 04 Dec 2005 10:41:33 -0800 (PST) Received: by 10.64.153.16 with HTTP; Sun, 4 Dec 2005 10:41:33 -0800 (PST) Message-ID: <731083980512041041o27e363a0s@mail.gmail.com> Date: Sun, 4 Dec 2005 16:41:33 -0200 From: Rodrigo Hjort To: Brendan Duddridge Subject: Re: Postgresql Replication High Availability Cc: pgsql-admin@postgresql.org In-Reply-To: <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <731083980512021932v7b3236cdg@mail.gmail.com> <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.161 required=5 tests=[AWL=0.161] X-Spam-Score: 0.161 X-Spam-Level: X-Archive-Number: 200512/27 X-Sequence-Number: 19747 Brendam, We started testing Sequoia last week, and it reached our expectatives of High Availability and Load Balance. We still need to verify if the performance is not so degradated due to multiple clusters updating. What is the difference between Sequoia and p/cluster? I mean, the latter is a commercial solution offered by Continuent, the same producer of Sequoia. Our applications are based on JBoss, connecting to a PostgreSQL via JDBC. One of the greatest features we found on Sequoia is the URL style: "jdbc:sequoia://first_node:port,second_node:port/database" When a Sequoia Controller is down (eg: first_node), the JDBC tries another one (ie, second_node), and it occurs transparently to the application! The JDBC Driver handles it all alone! I don't know if with a pure PostgreSQL JDBC Driver and the Slony I + Heartbeat joint solution the application would perform the same behavior... 2005/12/3, Brendan Duddridge : > Hello Rodrigo, > > Have you (or anyone else on this list) had great success with > Sequoia? I've been reading a bit about it. It looks like it might > work for us for a high-availability solution. Do you think it's just > as good as using p/cluster? We're deploying to Mac OS X Server and it > looks like p/cluster only supports Linux on x86. > > Thanks, > > ____________________________________________________________________ > Brendan Duddridge | CTO | 403-277-5591 x24 | brendan@clickspace.com > > ClickSpace Interactive Inc. > Suite L100, 239 - 10th Ave. SE > Calgary, AB T2G 0V9 > > http://www.clickspace.com Regards, Rodrigo Hjort http://www.pr.gov.br