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 A6D4A9DCB91 for ; Mon, 28 Nov 2005 04:44:42 -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 47524-03-5 for ; Mon, 28 Nov 2005 04:44:41 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by postgresql.org (Postfix) with ESMTP id 3EFB99DCBD5 for ; Mon, 28 Nov 2005 04:44:36 -0400 (AST) Received: from web33106.mail.mud.yahoo.com (web33106.mail.mud.yahoo.com [68.142.206.87]) by svr2.postgresql.org (Postfix) with SMTP id 44716F0C35 for ; Mon, 28 Nov 2005 03:02:39 +0000 (GMT) Received: (qmail 26143 invoked by uid 60001); 28 Nov 2005 03:02:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FsNkMc6paIsXGUwSMuDoLXEZmuQbZDHylRk5/Bf57FuiVP61uq1FlwuYMnHboCXv6YbWrCjAUPZo1ujODWU5/vJmH4ar9Ok4Ns5/bH9cw8/dSkdNGKi+55cd36jsBCjtvfas126u0PZ3HAC2NF7hVrYZKlzZKsiQaLGt5CpaOJE= ; Message-ID: <20051128030239.26141.qmail@web33106.mail.mud.yahoo.com> Received: from [12.43.23.89] by web33106.mail.mud.yahoo.com via HTTP; Sun, 27 Nov 2005 19:02:38 PST Date: Sun, 27 Nov 2005 19:02:38 -0800 (PST) From: Christopher Smith Subject: Postgresql Replication High Availability To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1038678060-1133146958=:25402" Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.48 required=5 tests=[DNS_FROM_RFC_ABUSE=0.479, HTML_MESSAGE=0.001] X-Spam-Score: 0.48 X-Spam-Level: X-Archive-Number: 200511/319 X-Sequence-Number: 19692 --0-1038678060-1133146958=:25402 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I am currently looking into high availability solutions for Postgresql. I am designing system that should not have a single point of failure. 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 Postgresql? #3. Any other solutions viable for production environments? --------------------------------- Yahoo! Music Unlimited - Access over 1 million songs. Try it free. --0-1038678060-1133146958=:25402 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
I am currently looking into high availability solutions for Postgresql. 
 
I am designing system that should not have a single point of failure.  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 Postgresql?
 
 
#3. Any other solutions viable for production environments?


Yahoo! Music Unlimited - Access over 1 million songs. Try it free. --0-1038678060-1133146958=:25402--