Slony1 PostgreSQL Replication - DDL statements and slon exec command

Author

DDL statements and slon exec command

Adam Haberlach

2005-06-10, 8:24 pm

We just rolled out slony 1.05 for our production cluster today, and it seems
to be working like a charm. Now I need to determine a path for upgrades of
our application and its databases. For now, I am advocating the method of
breaking the mirror, upgrading the master, and then recreating a mirror,
since at the moment this takes only about 20 minutes. We would like to
explore the option of using the 'execute' statement to syncronize changes to
both machines.

If we alter tables to add/remove columns, will slony's triggers be properly
updated?
If we alter the database to add/remove tables, will we need to manually
update the mirror set, or does this happen automagically as well?

Thanks,

--
Adam Haberlach
Database Administrator
adam- luex2ndOlgNN8Ch2cx6n
ig@public.gmane.org

Christopher Browne

2005-06-10, 8:24 pm

Adam Haberlach wrote:

>
> We just rolled out slony 1.05 for our production cluster today, and it
> seems to be working like a charm. Now I need to determine a path for
> upgrades of our application and its databases. For now, I am
> advocating the method of breaking the mirror, upgrading the master,
> and then recreating a mirror, since at the moment this takes only
> about 20 minutes. We would like to explore the option of using the
> 'execute' statement to syncronize changes to both machines.
>
> If we alter tables to add/remove columns, will slony's triggers be
> properly updated?

As long as you do those alterations inside the "executed" script, then
yes, they will be properly updated.

> If we alter the database to add/remove tables, will we need to
> manually update the mirror set, or does this happen automagically as well?

If you are planning to drop replicated tables, then you need to use SET
DROP TABLE to drop them from replication.

Presumably that should be done before "EXECUTE SCRIPT"...

Sponsored Links