Replicating db structure changes - Mailing list pgsql-general

From Robby Russell
Subject Replicating db structure changes
Date
Msg-id 46A81E58.8010500@planetargon.com
Whole thread Raw
Responses Re: Replicating db structure changes  (Richard Huxton <dev@archonet.com>)
Re: Replicating db structure changes  (Magnus Hagander <magnus@hagander.net>)
List pgsql-general
Hey all,

I'm catching up the replication options for PostgreSQL and was looking
at slony, but was wondering if I could get some pointers.

If I understand the slony documentation correctly, it doesn't allow me
to send CREATE/ALTER TABLE/INDEX statements to the master and have those
replicate to the slaves. Am I mistaken? If this is the case, are there
any alternatives to slony that would allow this to happen? We're using
Rails migrations, which generate the corresponding SQL statements and
then runs those against the production database. This works great, but
we're not sure how to go about having those migrations properly affect
slave databases, without running execute statements through slonik.

Are there any other replication options that might work for what we're
trying to do?

Another option is to begin looking into building our own SQL generation
(compatible with Rails migrations) tool that generates slonik-friendly
scripts for changes to the database structure.

Thanks in advance,

Robby

--
Robby Russell
http://www.robbyonrails.com/
http://www.planetargon.com/

pgsql-general by date:

Previous
From: Chris
Date:
Subject: Re: postgresql insert and dataset(c#)
Next
From: "Pavel Stehule"
Date:
Subject: Re: C function problem with 8.2.4