Replicating db structure changes
От | Robby Russell |
---|---|
Тема | Replicating db structure changes |
Дата | |
Msg-id | 46A81E58.8010500@planetargon.com обсуждение исходный текст |
Ответы |
Re: Replicating db structure changes
Re: Replicating db structure changes |
Список | 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 по дате отправления: