Re: rubyrep breaks Silver Stripe (MVC frame work) and vis versa.

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: rubyrep breaks Silver Stripe (MVC frame work) and vis versa.
Date: 2011-01-20 15:57:05
Message-ID: AANLkTimgcA0xWTLNUVLWBQ3K=MWLqPdoHo43O13b9_tq@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jan 20, 2011 at 1:49 AM, Gregory Machin <gdm(at)linuxpro(dot)co(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Paresi 2011-01-20 16:37:01 Moving from SQL Anywhere to PostGres - First Time
Previous Message Adrian Klaver 2011-01-20 15:17:03 Re: Problems with pg_dump/restore and OIDs