On Wed, Jul 25, 2007 at 09:08:56PM -0700, Robby Russell wrote: > 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? Are you looking for failover or loadsharing? If it's just failover, PITR warm standby should have no problem with DDL. But you can't do queries against the slave until after a failover... //Magnus ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
