Re: rubyrep breaks Silver Stripe (MVC frame work) and vis versa. - Mailing list pgsql-general

From Vick Khera
Subject Re: rubyrep breaks Silver Stripe (MVC frame work) and vis versa.
Date
Msg-id AANLkTimgcA0xWTLNUVLWBQ3K=MWLqPdoHo43O13b9_tq@mail.gmail.com
Whole thread Raw
In response to rubyrep breaks Silver Stripe (MVC frame work) and vis versa.  (Gregory Machin <gdm@linuxpro.co.za>)
List pgsql-general
On Thu, Jan 20, 2011 at 1:49 AM, Gregory Machin <gdm@linuxpro.co.za> wrote:
> In short how can I get "Hot standby" / master-master replication that
> will be transparent to the changes made by Silver Stripe, that will
> work with Postgresql 8.4.4.
>

The only replication system I know of that does not need to be aware
of the schema structure (and therefore must be aware of changes made
to it) is the hot standby built into postgres.  However, that does not
get you master/master which you seem to want.

I do not think your set of requirements can all be fulfilled.  You
will have to adjust one or more of them.  I'll venture to say that the
best target is to adjust the ORM's "update" process to be aware of
your replication strategy, and work with it rather than assume it has
full control over the DB.

pgsql-general by date:

Previous
From: Gregory Machin
Date:
Subject: rubyrep breaks Silver Stripe (MVC frame work) and vis versa.
Next
From: "Robert Paresi"
Date:
Subject: Moving from SQL Anywhere to PostGres - First Time