Re: Cluster/Replication - Mailing list pgsql-admin

From Joshua D. Drake
Subject Re: Cluster/Replication
Date
Msg-id 20071019100626.09fd9e13@scratch
Whole thread Raw
In response to Cluster/Replication  (Sean Brown <sbrown@eaglepress.com>)
Responses Re: Cluster/Replication
List pgsql-admin
On Fri, 19 Oct 2007 12:43:40 -0400
Sean Brown <sbrown@eaglepress.com> wrote:

> I believe this has come up before, and I am still researching how to
> do this and figured asking was probably a good idea as hopefully I
> can either get some direction or someone can point me at something I
> haven't seen yet.

Why do you have a synchronous requirement?

>
> We are setting up a new database system that is going to act as our
> central database. We are planning to have a Master/Slave setup,
> originally with one slave but there is a strong possibility of
> adding a second slave at our second site. We could run Mulit-Master,
> it just wasn't the original plan. (The original plan was MySQL log
> shipping). We do not want the possibility of loosing data in the
> event of loosing the master node so synchronous replication is
> preferable. We are using BLOBS, so the replication has to be able to
> handle that. The slave we want to have useable but it would be used
> for reporting only under normal usage.
>
> Slony is out because of the BLOB requirement and it's asynchronous.
> We are looking at pgCluster, but the replication server looks like a
> single point of failure itself. Also we're not really clear on how
> the replication server or load balancer operates for determining the
> load and size of the system it would have to run them on.
>
> There are a few other things like how to handle postgresql version
> upgrades but thats probably best left to specific forums once a
> solution is chosen.
>
> Is pgCluster the way to go or are there other projects we might want
> to look at?
>
> Thank you in advance.
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 1: if posting/reading
> through Usenet, please send an appropriate subscribe-nomail command
> to majordomo@postgresql.org so that your message can get through to
> the mailing list cleanly
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997  http://www.commandprompt.com/
            UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


Attachment

pgsql-admin by date:

Previous
From: Sean Brown
Date:
Subject: Cluster/Replication
Next
From: "Scott Marlowe"
Date:
Subject: Re: Trigger AFTER UPDATE OR INSERT