pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brendan Duddridge <brendan@clickspace.com>
To: Rodrigo Hjort <rodrigo.hjort@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql Replication High Availability
Date: Sat, 3 Dec 2005 15:46:35 -0700
Message-ID: <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com> (raw)
In-Reply-To: <731083980512021932v7b3236cdg@mail.gmail.com>
References: <731083980512021932v7b3236cdg@mail.gmail.com>

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

On Dec 2, 2005, at 8:32 PM, Rodrigo Hjort wrote:

> 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.
> 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?
>
> ------
>
> Regards,
>
> Rodrigo Hjort
>
> Linux User #348191 (http://counter.li.org)
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faq
>

Attachments:

  smime.p7s (application/pkcs7-signature, 2.3K) download

view thread (6+ messages)  latest in thread

Message-ID: <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com>
Permalink:  ../8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com/
Also on:    postgresql.org/message-id/8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: brendan@clickspace.com, rodrigo.hjort@gmail.com
  Subject: Re: Postgresql Replication High Availability
  In-Reply-To: <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com>
  References: <731083980512021932v7b3236cdg@mail.gmail.com> <8C2FC712-48C3-41BA-8596-3052B2B75A25@clickspace.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox